JavascriptCore

WebKit
Original author(s) KDE[1][2]
Developer(s) Apple, Adobe, and others
Initial release November 4, 1998; 15 years ago (1998-11-04) (KHTML released)
June 7, 2005; 9 years ago (2005-06-07) (WebKit open sourced)
Written in C++
Operating system Cross-platform[3]
Type Layout engine
License GNU LGPL v2.1 (some files in the JavaScriptCore & WebCore components), BSD v2.0 (most of browser engine)
Website

WebKit is a layout engine software component designed to allow web browsers to render web pages. It powers Apple's Safari web browser and Google's Chrome web browser versions up to 27 (except for iOS versions that still continue to use WebKit) applications. As of September 2013 WebKit browser market share[4] is ahead of both the Trident engine used by Internet Explorer, and the Gecko engine used by Firefox.

It is also used as the basis for the experimental browser included with the Amazon Kindle e-book reader, as well as the default browser in the Apple iOS, Android, BlackBerry 10, and Tizen mobile operating systems. WebKit's C++ API provides a set of classes to display web content in windows, and implements browser features such as following links when clicked by the user, managing a back-forward list, and managing a history of pages recently visited.

WebKit's HTML and JavaScript code originally began as a fork of the KHTML and KJS libraries from KDE,[5] and has now been further developed by individuals from KDE, Apple, Google, Nokia, Bitstream, BlackBerry, Igalia, and others.[6] OS X, Windows, GNU/Linux, and some other Unix-like operating systems are supported by the project.[7] On April 3, 2013 Google announced that it had forked WebCore, a component of WebKit to be used in future versions of Google Chrome and Opera.[8][9]

WebKit's WebCore and JavaScriptCore components are available under the GNU Lesser General Public License, and the rest of WebKit is available under a BSD-form license.[10] As of March 7, 2013, WebKit is a trademark of Apple, registered with the U.S. Patent and Trademark Office.[11]

Origins

The code that would become WebKit began in 1998 as the KDE's HTML layout engine KHTML and KDE's JavaScript engine (KJS). The WebKit project was started within Apple by Don Melton on June 25, 2001[12] as a fork of KHTML and KJS. Melton explained in an e-mail to KDE developers[2] that KHTML and KJS allowed easier development than other available technologies by virtue of being small (fewer than 140,000 lines of code), cleanly designed and standards-compliant. KHTML and KJS were ported to OS X with the help of an adapter library and renamed WebCore and JavaScriptCore.[2] JavaScriptCore was announced in an e-mail to a KDE mailing list in June 2002, alongside the first release of Apple's changes.[13] WebCore was announced at the Macworld Expo in January 2003 by Apple CEO Steve Jobs with the release of the Safari web browser. JavaScriptCore was first included with Mac OS X v10.2 as a private framework which Apple used within their Sherlock application, while WebCore debuted with the first beta of Safari. Mac OS X v10.3 was the first major release of Apple's operating system to bundle WebKit, although it had already been bundled with a minor release of 10.2.

According to Apple, some changes involved OS X–specific features (e.g., Objective-C, KWQ,[14] OS X calls) that are absent in KDE's KHTML, which called for different development tactics.[15]

Split development

The exchange of code between WebCore and KHTML was increasingly difficult as the code base diverged because both projects had different approaches in coding and code sharing.[16] At one point KHTML developers said they were unlikely to accept Apple's changes and claimed the relationship between the two groups was a "bitter failure".[17] Apple submitted their changes in large patches that contained a great number of changes with inadequate documentation, often to do with future additions. Thus, these patches were difficult for the KDE developers to integrate back into KHTML.[18] Furthermore, Apple had demanded that developers sign non-disclosure agreements before looking at Apple's source code and even then they were unable to access Apple's bug database.

During the publicized 'divorce' period, KDE developer Kurt Pfeifle (pipitas) posted an article claiming KHTML developers had managed to backport many (but not all) Safari improvements from WebCore to KHTML, and they always appreciated the improvements coming from Apple and still do so. The article also noted Apple had begun to contact KHTML developers about discussing how to improve the mutual relationship and ways of future cooperation.[19] In fact, the KDE project was able to incorporate some of these changes to improve KHTML's rendering speed and add features, including compliance with the Acid2 rendering test.[20]

Since the story of the fork appeared in news, Apple has released changes of the source code of WebKit fork in a CVS repository.[21] Since the transfer of the sourcecode into a public CVS repository, Apple and KHTML developers have had increasing collaboration. Many KHTML developers have become reviewers and submitters for WebKit SVN repository.

The WebKit team had also reversed many Apple-specific changes in the original WebKit code base and implemented platform-specific abstraction layers to make committing the core rendering code to other platforms significantly easier.[22]

In July 2007, the Ars Technica website published an article reporting that the KDE team would move from KHTML to WebKit.[23] Instead, after several years of integration, KDE Development Platform version 4.5.0 was released in August 2010 with support for both WebKit and KHTML, and development of KHTML continues.[24]

Open-sourcing

On June 7, 2005, Safari developer Dave Hyatt announced on his weblog that Apple was open-sourcing WebKit (previously, only WebCore and JavaScriptCore were open source) and opening up access to WebKit's CVS tree and the bug Database tool.[21] This was announced at Apple's Worldwide Developers Conference 2005 by Apple Senior Vice President of Software Engineering Bertrand Serlet.

In mid-December 2005 support for Scalable Vector Graphics was merged into the standard build[25] and in early January 2006 the source code was migrated from CVS to Subversion.

WebKit's JavaScriptCore and WebCore components are available under the GNU Lesser General Public License, while the rest of WebKit is available under a BSD-style license.

Further development

Beginning in early 2007, the development team began to implement Cascading Style Sheets (CSS) extensions, including animation, transitions and both 2D and 3D transforms;[26] such extensions were released as working drafts to the World Wide Web Consortium (W3C) in 2009 for standardization.[27]

In November 2007, the project announced that it had accomplished support for HTML5 media features, allowing for embedded video to be natively rendered and script-controlled in WebKit.[28]

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[29][30] The project evolved into SquirrelFish Extreme (abbreviated SFX), announced on September 18, 2008, which compiles JavaScript into native machine code, eliminating the need for a bytecode interpreter and thus speeding up JavaScript execution.[31] Initially the only supported architecture for SFX was the x86 architecture, but at the end of January 2009 SFX was enabled for OS X on x86-64 architectures as it passes all tests on that platform.[32]

WebKit2

WebKit2 was announced on April 8, 2010. WebKit2's goal is to abstract the components that provide web rendering cleanly from their surrounding interface or application shell, creating a situation where, "web content (JavaScript, HTML, layout, etc) lives in a separate process from the application UI". This abstraction is intended to make WebKit2's reuse a more straightforward process than WebKit's. WebKit2 has "an incompatible API change from the original WebKit", which motivated its name change.[33]

Currently WebKit2 is available for Mac, Windows, GTK+, and MeeGo-Harmattan.[34][35]

Use

Non-mobile web browser statistics on
Chrome
  
44.06%
Internet Explorer
  
22.08%
Firefox
  
18.17%
Others
  
9.07%
Opera
  
3.38%
Safari
  
3.24%
Non-mobile web browser usage for visitors as of March 2013.[36]

WebKit is used as the rendering engine within Safari and was formerly used by Google's Chrome web browser on Windows, OS X, iOS and Android (however, Chrome only used WebCore, and also incorporated its own JavaScript engine and multi-process system).[37] Other applications on OS X make use of WebKit, such as Apple's e-mail client Mail and the 2008 version of Microsoft's Entourage personal information manager, both of which make use of WebKit to render e-mail messages with HTML content.

Installed base

New web browsers have been built around WebKit such as the S60 browser[38] on Symbian mobile phones, BlackBerry Browser (ver 6.0+), Midori, Chrome browser,[39][40] the Android Web browser, and the browser used in PlayStation 3 system software from version 4.10.[41] KDE's Rekonq web browser and Plasma Workspaces also use it as the native web rendering engine. WebKit has been adopted as the rendering engine in OmniWeb, iCab and Web (previously known as Epiphany) replacing their original rendering engines. Sleipnir started development for WebKit in its browser in 2012, and as of May 17, 2012, is in alpha 3 stages.[42] Epiphany supported both Gecko and WebKit for some time, but the team decided that Gecko's release cycle and future development plans would make it too cumbersome to continue supporting it. HP's webOS uses WebKit as the basis of its application runtime.[43] The latest interface update for Valve's Steam employs WebKit to render its interface and built-in browser.[44] WebKit is used to render HTML and run JavaScript in the Adobe Integrated Runtime application platform. In Adobe Creative Suite CS5, WebKit is used to render some parts of the user interface. As of the first half of 2010, an analyst estimated the cumulative number of mobile handsets shipped with a WebKit-based browser at 350 million.[45] As of February 2012, WebKit's market share at 36%, is equal to the market share of the Trident/MSHTML engine used to power Internet Explorer.[46] If this growth rate continues, total use of WebKit (Chrome, Safari, and smartphones/tablets) will surpass 50% by the end of 2012 and WebKit will lead in market share.[47]

Ports

The week after Hyatt's announcement of WebKit's open-sourcing, Nokia announced that it had ported WebKit to the Symbian operating system and was developing a browser based on WebKit for mobile phones running S60. Now named Web Browser for S60, it is used on Nokia, Samsung, LG, and other Symbian S60 mobile phones. Apple has also ported WebKit to iOS to run on the iPhone, iPod Touch and iPad, where it is used to render content in the device's web browser and e-mail software.[48] The Android mobile phone platform uses WebKit as the basis of its web browser[49] and the Palm Pre, announced January 2009, has an interface based on WebKit.[50] The Amazon Kindle 3 includes an experimental WebKit based browser.[51]

In June 2007, Apple announced that WebKit had been ported to Microsoft Windows as part of Safari. There are also ongoing ports for the open source operating systems Syllable,[52] Haiku[53] and AROS Research Operating System (AROS).[54]

WebKit has also been ported to several toolkits that support multiple platforms, such as the GTK+ toolkit,[55][56] Qt framework,[57] Adobe Integrated Runtime, Enlightenment Foundation Libraries (EFL), and the Clutter toolkit.[58] Qt Software (owned by Digia) includes the Qt port in the Qt 4.4 release. The Qt port of WebKit is also available to be used in Konqueror since version 4.1.[23] The Iris Browser on Qt also uses WebKit. The Enlightenment Foundation Libraries (EFL) port is under development (by Samsung and ProFUSION[59]) focusing the embedded and mobile systems, for use as stand alone browser, widgets/gadgets, rich text viewer and composer. The Clutter port is developed by Collabora and sponsored by Bosch.

There is also a project synchronized with WebKit (sponsored by Pleyo)[60] called Origyn Web Browser, which provides a meta-port to an abstract platform with the aim of making porting to embedded or lightweight systems quicker and easier.[61] This port is used for embedded devices such as set-top boxes, PMP and it has been ported into AmigaOS,[62][63] AROS[64] and MorphOS. MorphOS version 1.7 is the first version of Origyn Web Browser (OWB) supporting HTML5 media tags.[65][66]

Forks

On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component known as Blink. Chrome's developers decided to fork WebKit in order to allow greater freedom in implementing WebCore's features in the browser without causing conflicts upstream, and would also allow the simplification of its codebase through the removal of code for WebCore components that are not used by Chrome. In relation to Opera Software's announcement earlier in the year that it would switch to WebKit by means of the Chromium codebase, it was also confirmed that the Opera web browser would also switch to Blink.[37] Following the announcement, WebKit developers began discussions on the possible removal of Chrome-specific code from the engine in order to streamline its overall codebase.[67]

Components

WebCore

WebCore is a layout, rendering, and Document Object Model (DOM) library for HTML and SVG, developed by the WebKit project. Its complete source code is licensed under the GNU Lesser General Public License (LGPL). The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-C application programming interface to the C++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to be easily referenced by applications based on the Cocoa API; later versions also include a cross-platform C++ platform abstraction, and various ports provide additional APIs.

WebKit passes the Acid2 and Acid3 tests, with pixel-perfect rendering and no timing or smoothness issues on reference hardware.[68]

JavaScriptCore

JavaScriptCore is a framework that provides a JavaScript engine for WebKit implementations, and provides this type of scripting in other contexts within OS X.[13][69] JavaScriptCore is originally derived from KDE's JavaScript engine (KJS) library (which is part of the KDE project) and the PCRE regular expression library. Since forking from KJS and PCRE, JavaScriptCore has been improved with many new features and greatly improved performance.[70]

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[29][30] The project evolved into SquirrelFish Extreme (abbreviated SFX, marketed as Nitro), announced on September 18, 2008, which compiles JavaScript into native machine code, eliminating the need for a bytecode interpreter and thus speeding up JavaScript execution.[31]

Drosera

Drosera is a JavaScript debugger that was included with the nightly builds of WebKit.[71][72] It was named after Drosera, a genus of carnivorous plants. Drosera has been replaced by the inclusion of debugging functions in the Web Inspector.[73]

See also

Free software portal

References

External links

  • The WebKit Help Mailinglist Archive – WebKit Help mailinglist archive
  • SunSpider 1.0 JavaScript Benchmark