KHTML

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]

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).

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]