Jump to content

WebKit

From Wikipedia, the free encyclopedia
(Redirected fromJavaScriptCore)

WebKit
Original author(s)Apple Inc.[1][2]
Developer(s)Apple Inc.,Adobe Systems,Sony,KDE,Igalia,and others
Initial releaseNovember 4, 1998;25 years ago(1998-11-04)(KHTML released)
June 7, 2005;19 years ago(2005-06-07)(WebKit sourced)
Preview release
Nightly[3]
Repositorygithub/WebKit/WebKit
Written inC++[4]
Operating systemmacOS,iOS,Linux,[5]Microsoft Windows[6][7]
TypeBrowser engine
LicenseLGPLv2.1(rendering engine, JavaScript engine),BSD 2-Clause(additional contributions from Apple)[8]
Websitewebkit.org

WebKitis abrowser engineprimarily used inApple'sSafariweb browser, as well as all web browsers oniOSandiPadOS.WebKit is also used by thePlayStationconsoles starting with the PS3, theTizenmobile operating systems, theAmazon Kindlee-bookreader,Nintendo consolesstarting with the3DS Internet Browser,and the discontinuedBlackBerry Browser.

WebKit started as aforkof theKHTMLandKJSlibraries fromKDE,[1][9]and has since been further developed byKDEcontributors,Apple,Google,Nokia,[9]Bitstream,BlackBerry,Sony,Igalia,and others.[10]WebKit supportsmacOS,Windows,Linux,and various otherUnix-likeoperating systems.[11]On April 3, 2013, Google announced that it had forked WebCore, a component of WebKit, to be used in future versions ofGoogle Chromeand theOpera web browser,under the nameBlink.[12][13]

ItsJavaScriptengine, JavascriptCore, also powers theBunserver-side JS runtime,[14]as opposed toV8used byNode.jsandBlink.WebKit'sC++application programming interface(API) provides a set ofclassesto displayWebcontent inwindows,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 isopen sourceand available under theBSD 2-Clauselicense[15][8]with the exception of theWebCoreandJavaScriptCorecomponents, which are available under theGNU Lesser General Public License.As of March 7, 2013, WebKit is a trademark of Apple, registered with the U.S. Patent and Trademark Office.[16]

Origins

[edit]

The code that would become WebKit began in 1998 as theKDE HTML(KHTML) layout engine andKDE JavaScript(KJS) engine. The WebKit project was started within Apple by Lisa Melton on June 25, 2001,[17][18]as aforkofKHTMLandKJS.Melton explained in an e-mail to KDE developers[1]thatKHTMLandKJSallowed easier development than other available technologies by virtue of being small (fewer than 140,000lines of code), cleanly designed and standards-compliant. KHTML and KJS was ported tomacOSwith the help of an adapterlibraryand renamed WebCore and JavaScriptCore.[1]JavaScriptCore was announced in an e-mail to a KDEmailing listin June 2002, alongside the first release of Apple's changes.[19]

According to Apple, some changes which called for different development tactics involved macOS-specific features that are absent in KDE's KHTML, such asObjective-C,KWQ (pronounced "quack" ) an implementation of the subset of Qt required to make KHTML work on macOS written in Objective C++, and macOS calls.[20]

Split development

[edit]

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.[21]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".[22]They claimed Apple submitted their changes in large patches containing multiple changes with inadequate documentation, often in relation to future additions to the codebase. Thus, these patches were difficult for theKDEdevelopers to integrate back into KHTML.[23]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.[24]

During the publicized "divorce" period, KDE developer Kurt Pfeifle (pipitas) posted an article claiming KHTML developers had managed tobackportmany (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.[25]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 theAcid2rendering test.[26]

Following the appearance of a story of the fork in the news, Apple released the source code of the WebKit fork in a publicrevision-controlrepository.[27]

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

In July 2007,Ars Technicareported that the KDE team would move from KHTML to WebKit.[29]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 continued until 2016 before it was officially discontinued in 2023.[30][31]

Open-sourcing

[edit]

On June 7, 2005, Safari developerDave Hyattannounced on hisweblogthat Apple was open-sourcing WebKit (formerly, only WebCore and JavaScriptCore were open source) and opening up access to WebKit'srevision controltree and the issue tracker.[27]

In mid-December 2005, support forScalable Vector Graphics(SVG) was merged into the standard build.[32]

WebKit's JavaScriptCore and WebCore components are available under the GNU Lesser General Public License, while the rest of WebKit is available under the BSD 2-Clause license.[8]

Further development

[edit]

Beginning in early 2007, the development team began to implementCascading Style Sheets(CSS) extensions, includinganimation,transitions and both 2D and 3D transforms;[33]such extensions were released as working drafts to theWorld Wide Web Consortium(W3C) in 2009 for standardization.[34]

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

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", abytecodeinterpreter.[36][37]The project evolved into SquirrelFish Extreme (abbreviated SFX), announced on September 18, 2008, whichcompilesJavaScript into nativemachine code,eliminating the need for a bytecode interpreter and thus speeding up JavaScript execution.[38]Initially, the only supported processor architecture for SFX was thex86,but at the end of January 2009, SFX was enabled for macOS onx86-64as it passes all tests on that platform.[39]

WebKit2

[edit]

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

The WebKit2 targets were set to Linux, macOS, Windows,GTK,andMeeGo-Harmattan.[41][42]Safari for macOS switched to the new API with version 5.1.[43]Safari for iOS switched to WebKit2 with iOS 8.[44]

The original WebKit API has been renamed WebKitLegacy API.[45]WebKit2 API has been renamed just plain WebKit API.[46]

Use

[edit]
Usage share of web browsersaccording toStatCounter

WebKit is used as the rendering engine withinSafariand was formerly used byGoogle'sChromeweb browser on Windows, macOS, andAndroid(before version 4.4 KitKat). Chrome used only WebCore, and included its ownJavaScript enginenamedV8and a multiprocess system.[47]Chrome foriOScontinues to use WebKit because Apple requires that web browsers on that platform must do so.[48]Other applications on macOS and iOS make use of WebKit, such as Apple's e-mail clientMail,App Store, and the 2008 version of Microsoft'sEntouragepersonal information manager,both of which make use of WebKit to render HTML content.

Installed base

[edit]

New web browsers have been built around WebKit such as theS60browser[49]onSymbianmobile phones,BlackBerryBrowser (ver 6.0+),Midori,Chromebrowser,[50][51]theAndroidWeb browser before version 4.4 KitKat, and the browser used inPlayStation 3 system softwarefrom version 4.10.[52]KDE's Rekonq web browser andPlasma Workspacesalso use it as the native web rendering engine. WebKit has been adopted as the rendering engine inOmniWeb,iCabandWeb(formerly named Epiphany) andSleipnir,replacing their original rendering engines. GNOME's Web supported bothGeckoand 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.[53]webOSuses WebKit as the basis of its application runtime.[54]WebKit is used to render HTML and run JavaScript in theAdobe Integrated Runtimeapplication platform. InAdobe Creative SuiteCS5, 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.[55]By mid-April 2015, WebKitbrowser market sharewas 50.3%.[56]

Ports

[edit]

The week after Hyatt announced WebKit's open-sourcing, Nokia announced that it had ported WebKit to theSymbianoperating system and was developing a browser based on WebKit for mobile phones running S60. NamedWeb Browser for S60,it was used on Nokia, Samsung, LG, and other Symbian S60 mobile phones. Apple has also ported WebKit toiOSto run on theiPhone,iPod Touch,andiPad,where it is used to render content in the device's web browser and e-mail software.[57]TheAndroidmobile phone platform used WebKit (and later versions itsBlink fork) as the basis of its web browser[58][59][60]and thePalm Pre,announced January 2009, has an interface based on WebKit.[61]TheAmazon Kindle3 includes an experimental WebKit based browser.[62]

In June 2007, Apple announced that WebKit had been ported toMicrosoft Windowsas part of Safari. Although Safari for Windows was silently discontinued[63]by the company, WebKit's ports to Microsoft's operating system are still actively maintained.[64][65]The Windows port uses Apple's proprietary libraries to function and is used for iCloud[66]and iTunes[67]for Windows, whereas the "WinCairo" port is a fully open-source and redistributable port.[68][69]

GNOME Webis a major web browser on Linux that uses WebKitGTK.

WebKit has also been ported to several toolkits that support multiple platforms, such as theGTKtoolkit forLinux,under the nameWebKitGTKwhich is used by Eolie,[70]GNOME Web,[71][72]Adobe Integrated Runtime,Enlightenment Foundation Libraries(EFL), and theCluttertoolkit.[73]Qt Softwareincluded a WebKit port in the Qt 4.4 release as a module called QtWebKit[74](since superseded byQt WebEngine,which uses Blink instead). TheIris Browseron Qt also used WebKit. The Enlightenment Foundation Libraries (EFL) port – EWebKit – was developed (bySamsungand ProFusion[75]) focusing the embedded and mobile systems, for use as stand alone browser, widgets-gadgets, rich text viewer and composer.[citation needed]The Clutter port is developed byCollaboraand sponsored byRobert Bosch GmbH.

There was also a project synchronized with WebKit (sponsored by Pleyo)[76]calledOrigyn 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.[77]This port is used for embedded devices such asset-top boxes,PMP and it has been ported intoAmigaOS,[78][79]AROS[80]andMorphOS.MorphOS version 1.7 is the first version ofOrigyn Web Browser(OWB) supportingHTML5media tags.[81][82]

Web Platform for Embedded

[edit]

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

[edit]

On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component, to be namedBlink.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 toOpera Software's announcement earlier in the year that it would switch to WebKit by means of theChromiumcodebase, it was confirmed that theOpera web browserwould also switch to Blink.[47]Following the announcement, WebKit developers began discussions on removing Chrome-specific code from the engine to streamline its codebase.[83]WebKit no longer has any Chrome specific code (e.g., buildsystem, V8 JavaScript engine hooks, platform code, etc.).[citation needed]

Components

[edit]

WebCore

[edit]

WebCore is a layout, rendering, andDocument Object Model(DOM)libraryfor HTML andScalable Vector Graphics(SVG), developed by the WebKit project. Its full source code is licensed under theGNU Lesser General Public License(LGPL). The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-Capplication programming interfaceto theC++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to be easily referenced by applications based on theCocoa API;later versions also include across-platformC++ platform abstraction, and various ports provide more APIs.[citation needed]

WebKit passes theAcid2andAcid3tests, with pixel-perfect rendering and no timing or smoothness issues on reference hardware.[84]

JavaScriptCore

[edit]

JavaScriptCore is a framework that provides aJavaScript enginefor WebKit implementations, and provides this type of scripting in other contexts within macOS.[19][85]JavaScriptCore is originally derived fromKDE's JavaScript engine (KJS)library(which is part of the KDE project) and thePCREregular expressionlibrary. Since forking from KJS and PCRE, JavaScriptCore has been improved with many new features and greatly improved performance.[86]

On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", abytecodeinterpreter.[36][37]The project evolved into SquirrelFish Extreme (abbreviated SFX, marketed as Nitro), announced on September 18, 2008 further speeding up JavaScript execution.[38]

An optimizingjust-in-time(JIT) compiler namedFTLwas announced on May 13, 2014.[87]It usesLLVMto generate optimized machine code. "FTL" stands for "Fourth-Tier-LLVM", and unofficially forfaster-than-light,alluding to its speed.[88]As of February 15, 2016, the backend of FTL JIT is replaced by "Bare Bones Backend" (or B3 for short).[89]

See also

[edit]

References

[edit]
  1. ^abcd"'(fwd) Greetings from the Safari team at Apple Computer' – MARC ".Lists.kde.org. January 7, 2003.Archivedfrom the original on February 9, 2015.RetrievedMay 2,2017.
  2. ^"Safari is released to the world".Donmelton.RetrievedJanuary 13,2013.
  3. ^"WebKit Nightly Builds".WebKit.org.Archivedfrom the original on April 3, 2016.RetrievedMay 27,2014.
  4. ^"Code Style Guidelines".WebKit.org.Apple, Inc. November 7, 2015.Archivedfrom the original on May 1, 2017.RetrievedMay 2,2017.
  5. ^"WebKit Download".March 30, 2016.RetrievedAugust 14,2018.
  6. ^"WebKit on Windows | WebKit".WebKit.org.Apple, Inc. November 7, 2015.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  7. ^"BuildingCairoOnWindows – WebKit".trac.webkit.org.Apple, Inc. June 8, 2021.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  8. ^abcLicensing WebKit | WebKit
  9. ^ab"The WebKit Open Source Project".Archivedfrom the original on April 10, 2012.RetrievedApril 7,2012.
  10. ^Stachowiak, Maciej (November 9, 2008)."Companies and Organizations that have contributed to WebKit".WebKit Wiki.RetrievedNovember 17,2008.
  11. ^"The WebKit Open Source Project – Getting the Code".Webkit.org.Archivedfrom the original on March 6, 2016.RetrievedDecember 27,2010.
  12. ^Barth, Adam (April 3, 2013)."Chromium Blog: Blink: A rendering engine for the Chromium project".Blog.chromium.org.Archivedfrom the original on April 4, 2013.RetrievedJune 14,2013.
  13. ^Lawson, Bruce (April 3, 2013)."Bruce Lawson's personal site: Hello Blink".Brucelawson.co.uk.RetrievedJune 14,2013.
  14. ^Omolana, Timilehin (August 2, 2022)."What Is Bun.js and Why Is the JavaScript Community Excited About It?".makeuseof.RetrievedMay 30,2023.
  15. ^"Open Source – WebKit".Apple. Archived fromthe originalon March 11, 2009.RetrievedMarch 5,2009.
  16. ^Purcher, Jack (March 7, 2013)."Apple's" WebKit "is now a Registered Trademark in the US".Patently Apple.Archivedfrom the original on March 9, 2013.RetrievedMarch 7,2013.
  17. ^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.Archivedfrom the original on April 20, 2021.RetrievedOctober 13,2011.
  18. ^Henry, Charlotte (June 25, 2021)."Happy 20th Birthday, Safari and Webkit!".The Mac Observer.RetrievedAugust 12,2023.
  19. ^abStachowiak, Maciej(June 13, 2002)."JavaScriptCore, Apple's JavaScript framework based on KJS".kde-darwin(Mailing list). Archived fromthe originalon March 10, 2007.RetrievedAugust 21,2008.
  20. ^"Safari and KHTML again".kdedevelopers.org. April 30, 2005. Archived from the original on March 3, 2006.RetrievedFebruary 20,2010.{{cite web}}:CS1 maint: unfit URL (link)
  21. ^"So, when will KHTML merge all the WebCore changes?".kdedevelopers.org. Archived from the original on May 29, 2010.RetrievedFebruary 20,2010.{{cite web}}:CS1 maint: unfit URL (link)
  22. ^"The bitter failure named 'safari and khtml'".Archivedfrom the original on April 15, 2015.
  23. ^"Open-source divorce for Apple's Safari?".Archivedfrom the original on July 7, 2009.
  24. ^"WebCore open source changes".Archived fromthe originalon May 27, 2016.RetrievedMay 14,2016.
  25. ^"WebCore – KHTML – Firefox: Know your facts!".Archived from the original on February 10, 2009.{{cite web}}:CS1 maint: unfit URL (link)
  26. ^"Konqueror now passes Acid2".Archivedfrom the original on June 21, 2017.
  27. ^abMolkentin, Daniel (June 7, 2005)."Apple Opens WebKit CVS and Bug Database".KDE News.Archivedfrom the original on July 15, 2009.RetrievedJanuary 16,2007.
  28. ^"Ars at WWDC: Interview with Lars Knoll, creator of KHTML".June 12, 2007.Archivedfrom the original on May 31, 2008.
  29. ^Unrau, Troy (July 23, 2007)."The unforking of KDE's KHTML and WebKit".Ars Technica.Archivedfrom the original on September 30, 2007.RetrievedJuly 30,2007.
  30. ^ "KDE Development Platform 4.5.0 gains performance, stability, new high-speed cache and support for WebKit".Archivedfrom the original on March 14, 2011.
  31. ^"KHTML repository".GitHub.RetrievedMay 5,2023.Removed for KF6, the 'kf5' branch contains the last maintained state.
  32. ^"Next Generation KDE Technologies Ported to WebCore".July 10, 2005.Archivedfrom the original on October 13, 2007.
  33. ^"CSS Transforms".Webkit.October 26, 2007.Archivedfrom the original on January 13, 2017.
  34. ^"CSS3 Animations".Archivedfrom the original on February 21, 2009.
  35. ^Koivisto, Antti (November 12, 2007)."HTML5 Media Support".Surfin' Safari blog.Archivedfrom the original on January 13, 2017.
  36. ^ab"Announcing SquirrelFish".June 2, 2008.Archivedfrom the original on January 27, 2017.
  37. ^ab"SquirrelFish project".
  38. ^ab"Introducing SquirrelFish Extreme".September 18, 2008.Archivedfrom the original on November 26, 2016.
  39. ^"Changeset 40439 – WebKit".Trac.webkit.org. January 30, 2009.RetrievedDecember 27,2010.
  40. ^"WebKit2 wiki".Webkit.org.RetrievedAugust 3,2012.
  41. ^"Announcing WebKit2".Webkit.org. April 8, 2010.Archivedfrom the original on April 23, 2011.RetrievedDecember 27,2010.
  42. ^"Introducing the Nokia N9: all it takes is a swipe! |Nokia Conversations – The official Nokia Blog".Nokia Corporation. Archived fromthe originalon June 24, 2011.RetrievedJune 21,2011.
  43. ^"Source code repository for public parts of Safari 5.1".The WebKit Open Source Project.RetrievedJuly 20,2011.
  44. ^"WWDC 2014 Session 206 - Introducing the Modern WebKit API - ASCIIwwdc".Archived fromthe originalon December 13, 2014.RetrievedDecember 13,2014.
  45. ^"132399 – Move the legacy WebKit API into WebKitLegacy.framework and move it inside WebKit.framework".Webkit.org.
  46. ^"Renaming Directories and Project Files to Match Framework Names".Webkit.org. July 10, 2017.
  47. ^"App Store Review Guidelines".
  48. ^"Nokia S60 Webkit Browser".Nokia. Archived fromthe originalon December 6, 2005.
  49. ^"Google Chrome, Google's Browser Project".Archivedfrom the original on September 2, 2008.
  50. ^"Comic describing the Google Chrome Project".Archivedfrom the original on September 3, 2008.
  51. ^"PS3, ファームウェアv4.10からWebKitへ. - あまた の gì かしら.".D.hatena.ne.jp. February 8, 2012.Archivedfrom the original on October 14, 2012.RetrievedJanuary 13,2013.
  52. ^"Epiphany Mailing list –Announcement: The Future of Epiphany".Archivedfrom the original on February 14, 2012.
  53. ^Chen, Brian X."HP Launches WebOS-Powered Tablet, Phones | Gadget Lab".Wired.Archivedfrom the original on April 10, 2014.RetrievedJanuary 13,2013.
  54. ^"100 Million Club (H1 2010 update)".VisionMobile.Archivedfrom the original on March 1, 2011.RetrievedMarch 1,2011.
  55. ^"StatCounter".StatCounter.Archivedfrom the original on May 26, 2012.RetrievedApril 14,2015.
  56. ^Stachowiak, Maciej (January 10, 2007)."The Obligatory iPhone Post".Surfin' Safari weblog.Archivedfrom the original on February 19, 2008.RetrievedJanuary 24,2008.
  57. ^"Android Uses WebKit".Archived fromthe originalon January 13, 2017.RetrievedJanuary 12,2017.
  58. ^"WebKit in the News".WebKit.November 13, 2007.RetrievedNovember 17,2018.
  59. ^"The Amazing Rise of WebKit Mobile".gigaom.November 13, 2007.RetrievedNovember 17,2018.
  60. ^"Palm Pre in-depth impressions, video, and huge hands-on gallery".January 9, 2009.Archivedfrom the original on January 13, 2017.
  61. ^Topolsky, Joshua (July 28, 2010)."New Amazon Kindle announced: $139 WiFi-only version and $189 3G model available August 27th in the US and UK".Archivedfrom the original on January 13, 2017.
  62. ^Lex Friedman (July 26, 2012)."Safari 6 available for Mountain Lion and Lion, but not Windows".macworld.International Data Group.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  63. ^"Buildbot: builder Apple-Win-10-Debug-Build".build.webkit.org.Apple, Inc.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  64. ^"Buildbot: builder WinCairo-64-bit-WKL-Release-Build".build.webkit.org.Apple, Inc.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  65. ^"About the security content of iCloud for Windows 12.3 - Apple Support".support.apple.Apple, Inc.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  66. ^"About the security content of iTunes 12.11.3 for Windows - Apple Support".support.apple.Apple, Inc.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  67. ^"BuildingCairoOnWindows – WebKit".trac.webkit.org.Apple, Inc. June 8, 2021.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  68. ^"GitHub - WebKitForWindows/WebKitRequirements: Build scripts for the requirements of the WinCairo port of WebKit".github.Apple, Inc.Archivedfrom the original on August 8, 2021.RetrievedAugust 8,2021.
  69. ^"World / Eolie".
  70. ^"WebKitGTK+ project website".Archivedfrom the original on January 30, 2017.
  71. ^"Alp Toker – WebKit/Gtk+ is coming".June 12, 2007.Archivedfrom the original on March 25, 2008.
  72. ^"WebKitClutter project website".
  73. ^"QT WebKit".Archived fromthe originalon August 3, 2009.
  74. ^"ProFusion | Home".Profusion.mobi.RetrievedJanuary 13,2013.
  75. ^"pleyo".Archivedfrom the original on March 25, 2008.
  76. ^"See OWB forge".Archivedfrom the original on May 9, 2008.
  77. ^"AmigaOS OWB official page".
  78. ^"Amiga – Powering through, dead or alive!".amigaweb.net. Archived fromthe originalon May 2, 2008.RetrievedJune 2,2010.
  79. ^"AROS OWB developer page".Archived fromthe originalon March 4, 2009.
  80. ^"Origyn Web Browser for MorphOS".Fabian Coeurjoly.Archivedfrom the original on March 17, 2010.RetrievedJanuary 4,2010.
  81. ^Holwerda, Thom (March 8, 2010)."Origyn Web Browser 1.7 Supports HTML5 Media, More".OSNews.Archivedfrom the original on March 12, 2010.RetrievedMarch 8,2010.
  82. ^"WebKit developers planning Chromium extraction".The H.Archivedfrom the original on April 7, 2013.RetrievedApril 9,2013.
  83. ^Stachowiak, Maciej (September 25, 2008)."Full Pass Of Acid3".Surfin' Safari – The WebKit Blog.Archivedfrom the original on September 29, 2008.RetrievedSeptember 29,2008.
  84. ^"The WebKit Open Source Project – JavaScript".Archivedfrom the original on August 14, 2015.
  85. ^"The Great Browser JavaScript Showdown".December 19, 2007.Archivedfrom the original on September 6, 2008.
  86. ^"Introducing the WebKit FTL JIT".Webkit.May 13, 2014.Archivedfrom the original on January 19, 2017.
  87. ^"Apple integrates LLVM compiler to boost WebKit JavaScript performance".May 16, 2014.Archivedfrom the original on July 8, 2017.
  88. ^"Introducing the B3 JIT Compiler".February 15, 2016.Archivedfrom the original on May 3, 2017.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=WebKit&oldid=1243227746#JavaScriptCore"