Editing WebKit (section)

== Use ==
[[File:Usage share of web browsers (Source StatCounter).svg|thumb|right|[[Usage share of web browsers]] according to [[StatCounter]]]]
WebKit is used as the rendering engine within [[Safari (web browser)|Safari]] and was used by [[Google]]'s [[Google Chrome|Chrome]] web browser on Windows, macOS, and [[Android (operating system)|Android]] (before version 4.4 KitKat). Chrome used only WebCore, and included its own [[JavaScript engine]] named [[Chrome V8|V8]] and a multiprocess system.<ref name="ars-blink" /> Chrome for [[iOS]] continues to use WebKit because Apple requires that web browsers on that platform must do so.<ref name="App Store Review Guidelines">{{cite web|url=https://developer.apple.com/app-store/review/guidelines/#software-requirements|title=App Store Review Guidelines}}</ref> Other applications on macOS and iOS make use of WebKit, such as Apple's e-mail client [[Mail (Apple)|Mail]], App Store, and the 2008 version of Microsoft's [[Microsoft Entourage|Entourage]] [[personal information manager]], both of which make use of WebKit to render HTML content.

=== Installed base ===
New web browsers have been built around WebKit such as the [[S60 (software platform)|S60]] browser<ref name="Nokia S60 Webkit Browser">{{cite web|url=http://opensource.nokia.com/projects/S60browser/|title=Nokia S60 Webkit Browser|publisher=Nokia|url-status=dead|archive-url=https://web.archive.org/web/20051206034449/http://opensource.nokia.com/projects/S60browser/|archive-date=December 6, 2005|df=mdy-all}}</ref> on [[Symbian]] mobile phones, [[BlackBerry OS|BlackBerry]] Browser (ver 6.0+), [[Midori (web browser)|Midori]], [[Google Chrome|Chrome]] browser,<ref name="Google Chrome, Google's Browser Project">{{cite web|url=http://blogoscoped.com/archive/2008-09-01-n47.html|title=Google Chrome, Google's Browser Project|url-status=live|archive-url=https://web.archive.org/web/20080902065842/http://blogoscoped.com/archive/2008-09-01-n47.html|archive-date=September 2, 2008|df=mdy-all}}</ref><ref name="google-comic">{{cite web|url=https://www.google.com/googlebooks/chrome/|title=Comic describing the Google Chrome Project|url-status=live|archive-url=https://web.archive.org/web/20080903142023/http://www.google.com/googlebooks/chrome/|archive-date=September 3, 2008|df=mdy-all}}</ref> the [[Android (operating system)|Android]] Web browsers before version 4.4 KitKat, and the browser used in [[PlayStation 3 system software]] from version 4.10.<ref>{{cite web |url=http://d.hatena.ne.jp/amatanoyo/20120208/1328681210 |title=PS3、ファームウェアv4.10からWebKitへ。 - あまたの何かしら。 |publisher=D.hatena.ne.jp |date=February 8, 2012 |access-date=January 13, 2013 |url-status=live |archive-url=https://web.archive.org/web/20121014094455/http://d.hatena.ne.jp/amatanoyo/20120208/1328681210 |archive-date=October 14, 2012 |df=mdy-all }}</ref> 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 (web browser)|Web]] (formerly named Epiphany) and [[Sleipnir (web browser)|Sleipnir]], replacing their original rendering engines. GNOME's Web supported both [[Gecko (layout engine)|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.<ref>{{cite web|url=http://mail.gnome.org/archives/epiphany-list/2008-April/msg00000.html|title=Epiphany Mailing list – ''Announcement: The Future of Epiphany''|url-status=live|archive-url=https://web.archive.org/web/20120214042734/http://mail.gnome.org/archives/epiphany-list/2008-April/msg00000.html|archive-date=February 14, 2012|df=mdy-all}}</ref> [[webOS]] uses WebKit as the basis of its application runtime.<ref>{{cite magazine |last=Chen |first=Brian X. |url=https://www.wired.com/2011/02/hp-web-os-tablet |title=HP Launches WebOS-Powered Tablet, Phones &#124; Gadget Lab |magazine=Wired |access-date=January 13, 2013 |url-status=live |archive-url=https://web.archive.org/web/20140410211728/http://www.wired.com/2011/02/hp-web-os-tablet |archive-date=April 10, 2014 |df=mdy-all }}</ref> 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.<ref>{{cite web|title=100 Million Club (H1 2010 update)|url=http://www.visionmobile.com/blog/2010/10/smart-feature-phones-the-unbalanced-equation-100-million-club-series/|publisher=VisionMobile|access-date=March 1, 2011|url-status=live|archive-url=https://web.archive.org/web/20110301192936/http://www.visionmobile.com/blog/2010/10/smart-feature-phones-the-unbalanced-equation-100-million-club-series/|archive-date=March 1, 2011|df=mdy-all}}</ref> By mid-April 2015, WebKit [[usage share of web browsers|browser market share]] was 50.3%.<ref>{{cite web|url=http://gs.statcounter.com/#browser-ww-monthly-201504-201504-bar/|title=StatCounter|publisher=StatCounter|access-date=April 14, 2015|url-status=live|archive-url=https://archive.today/20120526/http://gs.statcounter.com/%23mobile_browser-ww-monthly-201012-201111-bar#browser-ww-monthly-201504-201504-bar/|archive-date=May 26, 2012|df=mdy-all}}</ref>

=== {{Anchor|WebKitGTK}}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.<ref>{{cite web |url=https://webkit.org/blog/87/safari-on-the-iphone/ |title=The Obligatory iPhone Post |last=Stachowiak |first=Maciej |date=January 10, 2007 |work=Surfin' Safari weblog |access-date=January 24, 2008 |url-status=live |archive-url=https://web.archive.org/web/20080219013741/http://webkit.org/blog/87/safari-on-the-iphone/ |archive-date=February 19, 2008 |df=mdy-all }}</ref> The [[Android (operating system)|Android]] mobile phone platform used WebKit (and later versions its [[Blink (browser engine)|Blink fork]]) as the basis of its web browser<ref name="andport">{{cite web|url=https://webkit.org/blog/142/android-uses-webkit/|title=Android Uses WebKit|url-status=dead|archive-url=https://web.archive.org/web/20170113134900/https://webkit.org/blog/142/android-uses-webkit/|archive-date=January 13, 2017|df=mdy-all|access-date=January 12, 2017}}</ref><ref>{{Cite news|url=https://webkit.org/blog/143/webkit-in-the-news/|title=WebKit in the News|date=2007-11-13|work=WebKit|access-date=2018-11-17}}</ref><ref>{{Cite web|url=https://gigaom.com/2007/11/13/webkit/|title=The Amazing Rise of WebKit Mobile|date=2007-11-13|website=gigaom.com|language=en-US|access-date=2018-11-17}}</ref> and the [[Palm Pre]], announced January 2009, has an interface based on WebKit.<ref name="palmPre">{{cite web|url=https://www.engadget.com/2009/01/08/palm-pre-in-depth-impressions-video-and-huge-hands-on-gallery/|title=Palm Pre in-depth impressions, video, and huge hands-on gallery|date=January 9, 2009 |url-status=live|archive-url=https://web.archive.org/web/20170113134056/https://www.engadget.com/2009/01/08/palm-pre-in-depth-impressions-video-and-huge-hands-on-gallery/|archive-date=January 13, 2017|df=mdy-all}}</ref> The [[Amazon Kindle]] 3 includes an experimental WebKit based browser.<ref>{{cite web|url=https://www.engadget.com/2010/07/28/new-amazon-kindle-announced-139-wifi-only-version-and-189-3g/|title=New Amazon Kindle announced: $139 WiFi-only version and $189 3G model available August 27th in the US and UK|last=Topolsky|first=Joshua|date=July 28, 2010 |url-status=live|archive-url=https://web.archive.org/web/20170113134059/https://www.engadget.com/2010/07/28/new-amazon-kindle-announced-139-wifi-only-version-and-189-3g/|archive-date=January 13, 2017|df=mdy-all}}</ref>

In June 2007, Apple announced that WebKit had been ported to [[Microsoft Windows]] as part of Safari. Although Safari for Windows was silently discontinued<ref>{{cite web|title=Safari 6 available for Mountain Lion and Lion, but not Windows|author=Lex Friedman|date=July 26, 2012|website=macworld.com|publisher=International Data Group|language=en|url-status=live|url=https://www.macworld.com/article/218624/safari-6-available-for-mountain-lion-and-lion-but-not-windows.html|access-date=August 8, 2021|archive-url=https://web.archive.org/web/20210808110011/https://www.macworld.com/article/218624/safari-6-available-for-mountain-lion-and-lion-but-not-windows.html|archive-date=August 8, 2021|df=mdy-all}}</ref> by the company, WebKit's ports to Microsoft's operating system are still actively maintained.<ref>{{cite web|title=Buildbot: builder Apple-Win-10-Debug-Build|publisher=Apple, Inc.|website=build.webkit.org|language=en|url-status=live|access-date=August 8, 2021|url=https://build.webkit.org/#/builders/56|archive-url=https://archive.today/20210808113400/https://build.webkit.org/%23/builders/56|archive-date=August 8, 2021|df=mdy-all}}</ref><ref>{{cite web|title=Buildbot: builder WinCairo-64-bit-WKL-Release-Build|publisher=Apple, Inc.|website=build.webkit.org|language=en|url-status=live|url=https://build.webkit.org/#/builders/27|archive-url=https://archive.today/20210808112550/https://build.webkit.org/%23/builders/27|archive-date=August 8, 2021|df=mdy-all|access-date=August 8, 2021}}</ref> The Windows port uses Apple's proprietary libraries to function and is used for iCloud<ref>{{cite web|title=About the security content of iCloud for Windows 12.3 - Apple Support|publisher=Apple, Inc.|website=support.apple.com|language=en|url-status=live|access-date=August 8, 2021|url=https://support.apple.com/en-us/HT212321|archive-url=https://web.archive.org/web/20210808112027/https://support.apple.com/en-us/HT212321|archive-date=August 8, 2021|df=mdy-all}}</ref> and iTunes<ref>{{cite web|title=About the security content of iTunes 12.11.3 for Windows - Apple Support|publisher=Apple, Inc.|website=support.apple.com|language=en|url-status=live|access-date=August 8, 2021|url=https://support.apple.com/en-us/HT212319|archive-url=https://web.archive.org/web/20210808112513/https://support.apple.com/en-us/HT212319|archive-date=August 8, 2021|df=mdy-all}}</ref> for Windows, whereas the "WinCairo" port is a fully open-source and redistributable port.<ref>{{cite web|title=BuildingCairoOnWindows – WebKit|date=June 8, 2021|url=https://trac.webkit.org/wiki/BuildingCairoOnWindows|website=trac.webkit.org|publisher=Apple, Inc.|access-date=August 8, 2021|language=en|url-status=live|archive-url=https://web.archive.org/web/20210808103951/https://trac.webkit.org/wiki/BuildingCairoOnWindows|archive-date=August 8, 2021|df=mdy-all}}</ref><ref>{{cite web|title=GitHub - WebKitForWindows/WebKitRequirements: Build scripts for the requirements of the WinCairo port of WebKit|publisher=Apple, Inc.|website=github.com|language=en|url-status=live|access-date=August 8, 2021|url=https://github.com/WebKitForWindows/WebKitRequirements|archive-url=https://web.archive.org/web/20210808113405/https://github.com/WebKitForWindows/WebKitRequirements|archive-date=August 8, 2021|df=mdy-all}}</ref>
[[File:GNOME Web 47 - gnome.org.png|thumb|[[GNOME Web]] is a 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 Eolie,<ref>{{Cite web|url=https://gitlab.gnome.org/World/eolie|title=World / Eolie}}</ref> [[GNOME Web]],<ref name="gtkportweb">{{cite web|url=https://webkitgtk.org/|title=WebKitGTK+ project website|url-status=live|archive-url=https://web.archive.org/web/20170130054419/https://webkitgtk.org/|archive-date=January 30, 2017|df=mdy-all}}</ref><ref name="gtkport">{{cite web|url=http://www.atoker.com/blog/2007/06/12/webkitgtk-is-coming/|title=Alp Toker – WebKit/Gtk+ is coming|date=June 12, 2007|url-status=live|archive-url=https://web.archive.org/web/20080325050544/http://www.atoker.com/blog/2007/06/12/webkitgtk-is-coming/|archive-date=March 25, 2008|df=mdy-all}}</ref> [[Adobe Integrated Runtime]], [[Enlightenment Foundation Libraries]] (EFL), and the Clutter toolkit.<ref name="clutterportweb">{{cite web|url=https://trac.webkit.org/wiki/clutter|title=WebKitClutter project website}}</ref> [[Qt Software]] included a WebKit port in the Qt 4.4 release as a module called QtWebKit<ref name="Qt WebKit">{{cite web|url=http://www.qtsoftware.com/products/library/modular-class-library#info_webkit |title=QT WebKit |url-status=dead |archive-url=https://web.archive.org/web/20090803123246/http://www.qtsoftware.com/products/library/modular-class-library |archive-date=August 3, 2009}}</ref> (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<ref>{{cite web|url=http://profusion.mobi |title=ProFusion &#124; Home |publisher=Profusion.mobi |access-date=January 13, 2013}}</ref>) focusing the embedded and mobile systems, for use as stand alone browser, widgets-gadgets, rich text viewer and composer.{{Citation needed|date=February 2014}} The Clutter port is developed by [[Collabora]] and sponsored by [[Robert Bosch GmbH]].

There was also a project synchronized with WebKit (sponsored by Pleyo)<ref name="pleyo">{{cite web|url=http://www.pleyo.org|title=pleyo|url-status=live|archive-url=https://web.archive.org/web/20080325144513/http://www.pleyo.org/|archive-date=March 25, 2008|df=mdy-all}}</ref> 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.<ref name="owb">{{cite web|url=http://www.sand-labs.org/owb|title=See OWB forge|url-status=live|archive-url=https://web.archive.org/web/20080509022705/http://www.sand-labs.org/owb/|archive-date=May 9, 2008|df=mdy-all}}</ref> This port is used for embedded devices such as [[set-top box]]es, PMP and it has been ported into [[AmigaOS]],<ref name="owb_amiga">{{cite web|url=http://strohmayer.org/|title=AmigaOS OWB official page}}</ref><ref name="owb_AmigaOS3.9">{{cite web |url=http://amigaweb.net/index.php?function=view_news&id=962 |archive-url=https://web.archive.org/web/20080502200402/http://www.amigaweb.net/index.php?function=view_news&id=962 |url-status=dead |archive-date=May 2, 2008 |title=Amiga – Powering through, dead or alive! |publisher=amigaweb.net |access-date=June 2, 2010 }}</ref> [[AROS]]<ref name="owb_AROS">{{cite web|url=http://sszymczy.rootnode.net/index.php?menu=projects&submenu=owb|title=AROS OWB developer page|url-status=dead|archive-url=https://web.archive.org/web/20090304120818/http://sszymczy.rootnode.net/index.php?menu=projects&submenu=owb|archive-date=March 4, 2009|df=mdy-all}}</ref> and [[MorphOS]]. MorphOS version 1.7 is the first version of [[Origyn Web Browser]] (OWB) supporting [[HTML5]] media tags.<ref name=mosport>{{cite web |title=Origyn Web Browser for MorphOS |url=http://fabportnawak.free.fr/owb/ |publisher=Fabian Coeurjoly |access-date=January 4, 2010 |url-status=live |archive-url=https://web.archive.org/web/20100317031009/http://fabportnawak.free.fr/owb/ |archive-date=March 17, 2010 |df=mdy-all }}</ref><ref name=OWB_html5>{{cite web |title=Origyn Web Browser 1.7 Supports HTML5 Media, More |url=http://www.osnews.com/story/22971/Origyn_Web_Browser_1_7_Supports_HTML5_Media_More |publisher=OSNews |last=Holwerda |first=Thom |date=March 8, 2010 |access-date=March 8, 2010 |url-status=live |archive-url=https://web.archive.org/web/20100312050728/http://www.osnews.com/story/22971/Origyn_Web_Browser_1_7_Supports_HTML5_Media_More |archive-date=March 12, 2010 |df=mdy-all }}</ref>

==== 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. The WPE port is currently maintained by Igalia.

=== Forking by Google ===
On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component, to be named [[Blink (layout engine)|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 (web browser)|Chromium]] codebase, it was confirmed that the [[Opera (web browser)|Opera web browser]] would also switch to Blink.<ref name=ars-blink>{{cite web|title=Google going its own way, forking WebKit rendering engine|date=April 3, 2013|url=https://arstechnica.com/information-technology/2013/04/google-going-its-own-way-forking-webkit-rendering-engine/|publisher=Ars Technica|access-date=April 4, 2013|url-status=live|archive-url=https://web.archive.org/web/20130404014119/http://arstechnica.com/information-technology/2013/04/google-going-its-own-way-forking-webkit-rendering-engine/|archive-date=April 4, 2013|df=mdy-all}}</ref> Following the announcement, WebKit developers began discussions on removing Chrome-specific code from the engine to streamline its codebase.<ref name=h-webkitchrome>{{cite web|title=WebKit developers planning Chromium extraction|url=http://www.h-online.com/open/news/item/WebKit-developers-planning-Chromium-extraction-1835224.html|publisher=The H|access-date=April 9, 2013|url-status=live|archive-url=https://web.archive.org/web/20130407033029/http://www.h-online.com/open/news/item/WebKit-developers-planning-Chromium-extraction-1835224.html|archive-date=April 7, 2013|df=mdy-all}}</ref> WebKit no longer has any Chrome specific code (e.g., buildsystem, V8 JavaScript engine hooks, platform code, etc.).{{Citation needed|date=January 2024|reason=provide a link to release notes, official blog post or similar confirming this}}