WebKit

WebKit is a browser engine developed by Apple and primarily used in its Safari web browser, as well as all the iOS web browsers. WebKit is also used by the BlackBerry Browser, the Tizen mobile operating systems, and a browser included with the Amazon Kindle e-book reader. WebKit's C++ application programming interface (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
The WebKit logo, as of 2015
Original author(s)KDE[1][2]
Developer(s)Apple Inc., Adobe Systems, KDE, Igalia, and others
Initial releaseNovember 4, 1998 (1998-11-04) (KHTML released)
June 7, 2005 (2005-06-07) (WebKit sourced)
Preview release
Nightly[3]
Repository
Written inC++[4]
Operating systemmacOS, Linux[5]
TypeBrowser engine
LicenseLGPLv2.1 (rendering engine, JavaScript engine), BSD (additional contributions from Apple)
Websitewebkit.org

WebKit's HTML and JavaScript engine started as a fork of the KHTML and KJS libraries from KDE,[1][6] and has since been further developed by KDE contributors, Apple, Google, Nokia, Bitstream, BlackBerry, Igalia, and others.[7] WebKit supports macOS, Windows, Linux, and various other Unix-like operating systems.[8] 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 the Opera web browser, under the name Blink.[9][10]

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

Origins

The code that would become WebKit began in 1998 as the KDE HTML (KHTML) layout engine and KDE JavaScript (KJS) engine. The WebKit project was started within Apple by Don Melton on June 25, 2001,[13] as a fork of KHTML and KJS. Melton explained in an e-mail to KDE developers[1] 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.[1] JavaScriptCore was announced in an e-mail to a KDE mailing list in June 2002, alongside the first release of Apple's changes.[14] 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 in 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,[15] OS X calls) that are absent in KDE's KHTML, which called for different development tactics.[16]

Split development

The exchange of code between WebCore and KHTML became increasingly difficult as the code base diverged because both projects had different approaches in coding and code sharing.[17] 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".[18] Apple submitted their changes in large patches containing very many changes with inadequate documentation, often to do with future additions. Thus, these patches were difficult for the KDE developers to integrate back into KHTML.[19] Also, 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.[20]

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.[21] 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.[22]

Following the story of the fork's appearance in the news, Apple released changes of the source code of WebKit fork in a public revision-control repository.[23] Since the transfer of the source code into a public Concurrent Versions System (CVS) repository, Apple and KHTML developers have had increasing collaboration. Many KHTML developers have become reviewers and submitters for WebKit revision control 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.[24]

In July 2007, Ars Technica reported that the KDE team would move from KHTML to WebKit.[25] 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.[26]

Open-sourcing

On June 7, 2005, Safari developer Dave Hyatt announced on his weblog that Apple was open-sourcing WebKit (formerly, only WebCore and JavaScriptCore were open source) and opening up access to WebKit's revision control tree and the issue tracker.[23] 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 (SVG) was merged into the standard build[27] and in early January 2006 the source code was migrated from Concurrent Versions System (CVS) to Subversion (SVN).

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;[28] such extensions were released as working drafts to the World Wide Web Consortium (W3C) in 2009 for standardization.[29]

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

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[31][32] 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.[33] Initially, the only supported processor architecture for SFX was the x86, but at the end of January 2009, SFX was enabled for OS X on x86-64 as it passes all tests on that platform.[34]

WebKit2

On April 8, 2010, a project named WebKit2 was announced to redesign WebKit. Its goal was 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 was intended to make reuse a more straightforward process for WebKit2 than for WebKit. WebKit2 had "an incompatible API change from the original WebKit", which motivated its name change.[35]

The WebKit2 targets were set to Linux, MacOS, Windows, GTK, and MeeGo-Harmattan.[36][37] Safari for OS X switched to the new API with version 5.1.[38] Safari for iOS switched to WebKit2 since iOS 8.[39]

The original WebKit API has been renamed WebKitLegacy API.[40] WebKit2 API has been renamed just plain WebKit API.[41]

Use
Usage share of web browsers according to StatCounter

WebKit is used as the rendering engine within Safari and was formerly used by Google's Chrome web browser on Windows, macOS, iOS, and Android before version 4.4 KitKat (Chrome used only WebCore, and included its own JavaScript engine named V8 and a multiprocess system).[42] Other applications on macOS 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[43] on Symbian mobile phones, BlackBerry Browser (ver 6.0+), Midori, Chrome browser,[44][45] the Android Web browser before version 4.4 KitKat, and the browser used in PlayStation 3 system software from version 4.10.[46] 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 (formerly named Epiphany) and Sleipnir, replacing their original rendering engines. GNOME's Web 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.[47] webOS uses WebKit as the basis of its application runtime.[48] The latest interface update for Valve's Steam employs WebKit to render its interface and built-in browser.[49] 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.[50] By mid April 2015, WebKit browser market share was 50.3%.[51]

Ports

The week after Hyatt announced 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. Named Web Browser for S60, it was 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.[52] The Android mobile phone platform used WebKit (and later versions its Blink fork) as the basis of its web browser[53][54][55] and the Palm Pre, announced January 2009, has an interface based on WebKit.[56] The Amazon Kindle 3 includes an experimental WebKit based browser.[57]

In June 2007, Apple announced that WebKit had been ported to Microsoft Windows as part of Safari.

GNOME Web is a major web browser on Linux that uses WebKitGTK

WebKit has also been ported to several toolkits that support multiple platforms, such as the GTK toolkit for Linux, under the name WebKitGTK which is used by GNOME Web,[58][59] Adobe Integrated Runtime, Enlightenment Foundation Libraries (EFL), and the Clutter toolkit.[60] Qt Software included a WebKit port in the Qt 4.4 release as a module called QtWebKit[61] (since superseded by Qt WebEngine, which uses Blink instead). The Iris Browser on Qt also used WebKit. The Enlightenment Foundation Libraries (EFL) port – EWebKit – was developed (by Samsung and ProFusion[62]) 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 Robert Bosch GmbH.

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

Web Platform for Embedded

Web Platform for Embedded (WPE) is a WebKit port designed for embedded applications; it further improves the architecture by splitting the basic rendering functional blocks into a general-purpose routines library (libwpe), platform backends, and engine itself (called WPE WebKit). The GTK port, albeit self-contained, can be built to use these base libraries instead of its internal platform support implementation.

Forking by Google

On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component, to be named Blink. Chrome's developers decided on the fork to allow greater freedom in implementing WebCore's features in the browser without causing conflicts upstream, and to allow simplifying its codebase by removing code for WebCore components unused 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 confirmed that the Opera web browser would also switch to Blink.[42] Following the announcement, WebKit developers began discussions on removing Chrome-specific code from the engine to streamline its codebase.[70] WebKit no longer has any Chrome specific code (e.g., buildsystem, V8 JavaScript engine hooks, platform code, etc.).

Components

WebCore

WebCore is a layout, rendering, and Document Object Model (DOM) library for HTML and Scalable Vector Graphics (SVG), developed by the WebKit project. Its full 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 more APIs.

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

JavaScriptCore

JavaScriptCore is a framework that provides a JavaScript engine for WebKit implementations, and provides this type of scripting in other contexts within macOS.[14][72] 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.[73]

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[31][32] 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 JavaScript execution.[33]

An optimizing just-in-time (JIT) compiler named FTL was announced on May 13, 2014.[74] It uses LLVM to generate optimized machine code. "FTL" stands for "Fourth-Tier-LLVM", and unofficially for faster-than-light, alluding to its speed.[75] As of February 15, 2016, the backend of FTL JIT is replaced by "Bare Bones Backend" (or B3 for short).[76]

gollark: Or dashes!
gollark: ward (stupidly limited)fog (not possible for trades, stops people looking at stuff anyway, ineffective against existing sickness)
gollark: There are two viable methods:
gollark: Also, it's far, *far* easier to attack than defend eggs.
gollark: I wonder how long it'll be before an octillion people come complaining about my no-sickness suggestion.

See also

References
  1. "'(fwd) Greetings from the Safari team at Apple Computer' – MARC". Lists.kde.org. January 7, 2003. Archived from the original on February 9, 2015. Retrieved May 2, 2017.
  2. "Safari is released to the world". Donmelton.com. Retrieved January 13, 2013.
  3. "WebKit Nightly Builds". WebKit.org. Archived from the original on April 3, 2016. Retrieved May 27, 2014.
  4. "Code Style Guidelines". WebKit.org. Apple, Inc. Archived from the original on May 1, 2017. Retrieved May 2, 2017.
  5. "WebKit Download". Retrieved August 14, 2018.
  6. "The WebKit Open Source Project". Archived from the original on April 10, 2012. Retrieved April 7, 2012.
  7. Stachowiak, Maciej (November 9, 2008). "Companies and Organizations that have contributed to WebKit". WebKit Wiki. Retrieved November 17, 2008.
  8. "The WebKit Open Source Project – Getting the Code". Webkit.org. Archived from the original on March 6, 2016. Retrieved December 27, 2010.
  9. Barth, Adam (April 3, 2013). "Chromium Blog: Blink: A rendering engine for the Chromium project". Blog.chromium.org. Archived from the original on April 4, 2013. Retrieved June 14, 2013.
  10. Lawson, Bruce. "Bruce Lawson's personal site: Hello Blink". Brucelawson.co.uk. Retrieved June 14, 2013.
  11. "Open Source – WebKit". Apple. Archived from the original on March 11, 2009. Retrieved March 5, 2009.
  12. "Apple's "WebKit" is now a Registered Trademark in the US". Archived from the original on March 9, 2013. Retrieved March 7, 2013.
  13. Melton, Don (August 25, 2011). "Attention Internets! WebKit is not 10 years old today. That happened on June 25. I know the date because that's when I started the project". Twitter. Retrieved October 13, 2011.
  14. Stachowiak, Maciej (June 13, 2002). "JavaScriptCore, Apple's JavaScript framework based on KJS". kde-darwin (Mailing list). Archived from the original on March 10, 2007. Retrieved August 21, 2008.
  15. KWQ (pronounced "quack") is an implementation of the subset of Qt required to make KHTML work on OS X. It is written in Objective C++.
  16. "Safari and KHTML again". kdedevelopers.org. April 30, 2005. Archived from the original on March 3, 2006. Retrieved February 20, 2010.
  17. "So, when will KHTML merge all the WebCore changes?". kdedevelopers.org. Archived from the original on May 29, 2010. Retrieved February 20, 2010.
  18. "The bitter failure named 'safari and khtml'". Archived from the original on April 15, 2015.
  19. "Open-source divorce for Apple's Safari?". Archived from the original on July 7, 2009.
  20. "WebCore open source changes". Archived from the original on May 27, 2016. Retrieved May 14, 2016.
  21. "WebCore – KHTML – Firefox: Know your facts!". Archived from the original on February 10, 2009.
  22. "Konqueror now passes Acid2". Archived from the original on June 21, 2017.
  23. Molkentin, Daniel (June 7, 2005). "Apple Opens WebKit CVS and Bug Database". KDE News. Archived from the original on July 15, 2009. Retrieved January 16, 2007.
  24. "Ars at WWDC: Interview with Lars Knoll, creator of KHTML". Archived from the original on May 31, 2008.
  25. Unrau, Troy (July 23, 2007). "The unforking of KDE's KHTML and WebKit". Ars Technica. Archived from the original on September 30, 2007. Retrieved July 30, 2007.
  26. "KDE Development Platform 4.5.0 gains performance, stability, new high-speed cache and support for WebKit". Archived from the original on March 14, 2011.
  27. "Next Generation KDE Technologies Ported to WebCore". Archived from the original on October 13, 2007.
  28. "CSS Transforms". Archived from the original on January 13, 2017.
  29. "CSS3 Animations". Archived from the original on February 21, 2009.
  30. Koivisto, Antti (November 12, 2007). "HTML5 Media Support". Surfin' Safari blog. Archived from the original on January 13, 2017.
  31. "Announcing SquirrelFish". Archived from the original on January 27, 2017.
  32. "SquirrelFish project".
  33. "Introducing SquirrelFish Extreme". Archived from the original on November 26, 2016.
  34. "Changeset 40439 – WebKit". Trac.webkit.org. January 30, 2009. Retrieved December 27, 2010.
  35. "WebKit2 wiki". Webkit.org. Retrieved August 3, 2012.
  36. "Announcing WebKit2". Webkit.org. Archived from the original on April 23, 2011. Retrieved December 27, 2010.
  37. "Introducing the Nokia N9: all it takes is a swipe! |Nokia Conversations – The official Nokia Blog". Nokia Corporation. Archived from the original on June 24, 2011. Retrieved June 21, 2011.
  38. "Source code repository for public parts of Safari 5.1". The WebKit Open Source Project. Retrieved July 20, 2011.
  39. "WWDC 2014 Session 206 - Introducing the Modern WebKit API - ASCIIwwdc".
  40. "132399 – Move the legacy WebKit API into WebKitLegacy.framework and move it inside WebKit.framework". Webkit.org.
  41. "Renaming Directories and Project Files to Match Framework Names". Webkit.org.
  42. "Nokia S60 Webkit Browser". Archived from the original on December 6, 2005.
  43. "Google Chrome, Google's Browser Project". Archived from the original on September 2, 2008.
  44. "Comic describing the Google Chrome Project". Archived from the original on September 3, 2008.
  45. "PS3、ファームウェアv4.10からWebKitへ。 - あまたの何かしら。". D.hatena.ne.jp. February 8, 2012. Archived from the original on October 14, 2012. Retrieved January 13, 2013.
  46. "Epiphany Mailing list – Announcement: The Future of Epiphany". Archived from the original on February 14, 2012.
  47. Chen, Brian X. "HP Launches WebOS-Powered Tablet, Phones | Gadget Lab". Wired.com. Archived from the original on April 10, 2014. Retrieved January 13, 2013.
  48. "A Brand New Steam". Archived from the original on December 30, 2010.
  49. "100 Million Club (H1 2010 update)". VisionMobile. Archived from the original on March 1, 2011. Retrieved March 1, 2011.
  50. "StatCounter". StatCounter. Archived from the original on May 26, 2012. Retrieved April 14, 2015.
  51. Stachowiak, Maciej (January 10, 2007). "The Obligatory iPhone Post". Surfin' Safari weblog. Archived from the original on February 19, 2008. Retrieved January 24, 2008.
  52. "Android Uses WebKit". Archived from the original on January 13, 2017. Retrieved January 12, 2017.
  53. "WebKit in the News". WebKit. November 13, 2007. Retrieved November 17, 2018.
  54. "The Amazing Rise of WebKit Mobile". gigaom.com. November 13, 2007. Retrieved November 17, 2018.
  55. "Palm Pre in-depth impressions, video, and huge hands-on gallery". Archived from the original on January 13, 2017.
  56. Topolsky, Joshua. "New Amazon Kindle announced: $139 WiFi-only version and $189 3G model available August 27th in the US and UK". Archived from the original on January 13, 2017.
  57. "WebKitGTK+ project website". Archived from the original on January 30, 2017.
  58. "Alp Toker – WebKit/Gtk+ is coming". Archived from the original on March 25, 2008.
  59. "WebKitClutter project website".
  60. "QT WebKit". Archived from the original on August 3, 2009.
  61. "ProFusion | Home". Profusion.mobi. Retrieved January 13, 2013.
  62. "pleyo". Archived from the original on March 25, 2008.
  63. "See OWB forge". Archived from the original on May 9, 2008.
  64. "AmigaOS OWB official page".
  65. "Amiga – Powering through, dead or alive!". amigaweb.net. Archived from the original on May 2, 2008. Retrieved June 2, 2010.
  66. "AROS OWB developer page". Archived from the original on March 4, 2009.
  67. "Origyn Web Browser for MorphOS". Fabian Coeurjoly. Archived from the original on March 17, 2010. Retrieved January 4, 2010.
  68. Holwerda, Thom (March 8, 2010). "Origyn Web Browser 1.7 Supports HTML5 Media, More". OSNews. Archived from the original on March 12, 2010. Retrieved March 8, 2010.
  69. "WebKit developers planning Chromium extraction". The H. Archived from the original on April 7, 2013. Retrieved April 9, 2013.
  70. Stachowiak, Maciej (September 25, 2008). "Full Pass Of Acid3". Surfin' Safari – The WebKit Blog. Archived from the original on September 29, 2008. Retrieved September 29, 2008.
  71. "The WebKit Open Source Project – JavaScript". Archived from the original on August 14, 2015.
  72. "The Great Browser JavaScript Showdown". December 19, 2007. Archived from the original on September 6, 2008.
  73. "Introducing the WebKit FTL JIT". Archived from the original on January 19, 2017.
  74. "Apple integrates LLVM compiler to boost WebKit JavaScript performance". Archived from the original on July 8, 2017.
  75. "Introducing the B3 JIT Compiler". Archived from the original on May 3, 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.