KHTML

KHTML is a browser engine developed by the KDE project. It is the engine used by the Konqueror web browser. Although it has not seen significant development since 2016,[1] it is still actively maintained, and engines descended from KHTML are used by some of the world's most widely used browsers, among them Google Chrome, Safari, Opera, Vivaldi, Microsoft Edge. Distributed under the terms of the GNU Lesser General Public License, KHTML is free software.

KHTML
Konqueror using KHTML to render the Dutch Wikipedia front page in 2009
Developer(s)KDE
Stable release5.70.0 (May 2, 2020 (2020-05-02)) [±][1]
Preview release4.12.97 (March 27, 2014 (2014-03-27)) [±][2]
Repositoryhttps://invent.kde.org/frameworks/khtml
Written inC++[3]
TypeBrowser engine
LicenseGNU Lesser General Public License

Built on the KParts framework and written in C++, KHTML had relatively good support for Web standards. To render as many pages as possible, some extra abilities and quirks from Internet Explorer are also supported, even though those are non-standard.

History

Origins

KHTML was preceded by an earlier engine called khtmlw or the KDE HTML Widget, developed by Torben Weis and Martin Jones,[4][5] which implemented support for HTML 3.2, HTTP 1.0, and HTML frames, but not the W3C DOM, CSS, or scripting.

KHTML itself came into existence on November 4, 1998,[4] as a fork of the khtmlw library, with some slight refactoring and the addition of Unicode support and changes to support the move to Qt 2. Waldo Bastian[6] was among those who did the work of creating that early version of KHTML.[4]

Re-write and improvement

The real work on KHTML actually started between May and October 1999, with the realization that the choice facing the project was "either do a significant effort to move KHTML forward or to use Mozilla"[4] and with adding support for scripting as the highest priority. So in May 1999, Lars Knoll[7] began doing research with an eye toward implementing the W3C DOM specification, finally announcing[8] on August 16, 1999 that he had checked in[9] what amounted to a complete rewrite of the KHTML library—changing KHTML to use the standard W3C DOM as its internal document representation. That in turn allowed the beginnings of JavaScript support to be added in October 1999,[4] with the integration of Harri Porten's KJS following shortly afterwards.

In the closing months of 1999 and first few months of 2000, Knoll did further work with Antti Koivisto and Dirk Mueller[4][10][11] to add CSS support and to refine and stabilize the KHTML architecture,[4] with most of that work being completed by March 2000. Among other things, those changes enabled KHTML to become the second browser after Internet Explorer to correctly support Hebrew and Arabic and languages written right-to-left[4]—before Mozilla had such support.

KDE 2.0 was the first KDE release (on October 23, 2000) to include KHTML[12] (as the rendering engine of the new Konqueror file and web browser, which replaced the monolithic KDE File Manager).

Other modules

KSVG was first developed in 2001 by Nikolas Zimmermann and Rob Buis; however, by 2003, it was decided to fork the then-current KSVG implementation into two new projects: KDOM/KSVG2 (to improve the state of DOM rendering in KHTML underneath a more formidable SVG 1.0 render state) and Kcanvas (to abstract any rendering done within khtml/ksvg2 in a single shared library, with multiple backends for it, e.g., Cairo/Qt, etc.).[13]

KSVG2 is also a part of WebKit.[14]

Standards compliance

The following standards are supported by the KHTML engine:

Descendants

KHTML and KJS were adopted by Apple in 2002 for use in the Safari web browser. Apple publishes the source code for their fork of the KHTML engine, called WebKit. In 2013, Google began development on a fork of WebKit, called Blink.[16]

gollark: +>markov 258639553357676545 2
gollark: ++remind 5d anaardvarks
gollark: +>markov 258639553357676545 2
gollark: +>markov 258639553357676545 2
gollark: +>markov 258639553357676545 2

See also

References

  1. "KHTML commit log". Phabricator.kde.org. Retrieved 2019-03-06.
  2. "Index of ftp://ftp.kde.org/pub/kde/unstable/ ". Retrieved 2014-06-12.
  3. "KHTML repository analytics". invent.kde.org. Retrieved 2020-08-15.
  4. "Lars Knoll and George Staikos: From KDE to WebKit". YouTube. Retrieved 1 September 2019.
  5. "KDE/kde1-kdelibs/khtmlw". GitHub. Retrieved 2020-01-23.
  6. "Waldo Bastian | Behind KDE". Behindkde.org. Retrieved 1 September 2019.
  7. "Lars Knoll | Behind KDE". Behindkde.org. Retrieved 1 September 2019.
  8. "'changes in KHTML' - MARC". Marc.info. Retrieved 1 September 2019.
  9. "'khtml_to_dom: kdelibs/khtml' - MARC". Marc.info. Retrieved 1 September 2019.
  10. "WebKit Team – WebKit". Trac.webkit.org. Retrieved 1 September 2019.
  11. "Dirk Mueller | Behind KDE". Behindkde.org. Retrieved 1 September 2019.
  12. "Lars Knoll and George Staikos: From KDE to WebKit". YouTube. Retrieved 1 September 2019.
  13. "The WebKit Open Source Project". Webkit.org. Retrieved 1 September 2019.
  14. "KDE 3.5.6 Changelog". K Desktop Environment.
  15. "Blink: A rendering engine for the Chromium project". Blog.chromium.org. Retrieved 1 September 2019.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.