KHTML

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
KHTML
300px
Konqueror using KHTML to render the Dutch Wikipedia front page in 2009
Developer(s) KDE
Stable release 4.13.2 (June 6, 2014; 9 years ago (2014-06-06)) [±][1]
Preview release 4.12.97 (March 27, 2014; 10 years ago (2014-03-27)) [±][2]
Written in C++[3]
Type Browser engine
License GNU Lesser General Public License
Website {{#property:P856}}

KHTML is a browser engine developed by the KDE project. It is the default engine of the Konqueror browser, but it has not been actively worked on since 2016.[4] Moreover, KHTML will be discontinued for KDE Frameworks 6.[5]

Built on the KParts framework and written in C++, KHTML had relatively good support for Web standards during its prime. Engines descended from KHTML are used by some of the world's most widely used browsers, among them Google Chrome, Safari, Opera, Vivaldi, and Microsoft Edge.

History

Origins

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

KHTML itself came into existence on November 4, 1998,[6] 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[8] was among those who did the work of creating that early version of KHTML.[6]

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"[6] and with adding support for JavaScript as the highest priority. So in May 1999, Lars Knoll[9] began doing research with an eye toward implementing the W3C DOM specification, finally announcing[10] on August 16, 1999 that he had checked in[11] 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,[6] 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[6][12][13] to add CSS support and to refine and stabilize the KHTML architecture,[6] 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[6]—before Mozilla had such support.

KDE 2.0 was the first KDE release (on October 23, 2000) to include KHTML[14] (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.).[15]

KSVG2 is also a part of WebKit.[16]

Sunsetting

KHTML is set to be removed in KDE Frameworks 6.[5] It has not had active development since 2016, just the necessary maintenance to work with updates to Frameworks 5.[4]

Standards compliance

The following standards are supported by the KHTML engine:

<templatestyles src="Div col/styles.css"/>

Descendants

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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.[18]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Cite error: Invalid <ref> tag; no text was provided for refs named git_log
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. [1][permanent dead link]
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.

External links