Gecko (software)

Development of the layout engine now known as Gecko began at Netscape in 1997, following the company's purchase of DigitalStyle. The existing Netscape rendering engine, originally written for Netscape Navigator 1.0 and upgraded through the years, was slow, did not comply well with W3C standards, had limited support for dynamic HTML and lacked features such as incremental reflow (when the layout engine rearranges elements on the screen as new data is downloaded and added to the page). The new layout engine was developed in parallel with the old, with the intention being to integrate it into Netscape Communicator when it was mature and stable. At least one more major revision of Netscape was expected to be released with the old layout engine before the switch.

After the launch of the Mozilla project in early 1998, the new layout engine code was released under an open-source license. Originally unveiled as Raptor, the name had to be changed to NGLayout (next generation layout) due to trademark problems. Netscape later rebranded NGLayout as Gecko. While Mozilla Organization (the forerunner of the Mozilla Foundation) initially continued to use the NGLayout name (Gecko was a Netscape trademark),{{cite web|url=https://www.mozilla.org/newlayout/gecko.html |title=nglayout project: identity crisis |publisher=Mozilla.org |access-date=2012-10-31 |url-status=dead |archive-url=https://web.archive.org/web/20110629154746/http://www.mozilla.org/newlayout/gecko.html |archive-date=2011-06-29 }} eventually the Gecko branding won out.{{Citation needed|date=April 2023}}

In October 1998, Netscape announced that its next browser would use Gecko (which was still called NGLayout at the time) rather than the old layout engine, requiring large parts of the application to be rewritten. While this decision was popular with web standards advocates, it was largely unpopular with Netscape developers, who were unhappy with the six months given for the rewrite. It also meant that most of the work done for Netscape Communicator 5.0 (including development on the Mariner improvements to the old layout engine) had to be abandoned. Netscape 6, the first Netscape release to incorporate Gecko, was released in November 2000 (the name Netscape 5 was never used).{{Citation needed|date=April 2023}}

As Gecko development continued, other applications and embedders began to make use of it. America Online, by this time Netscape's parent company, eventually adopted it for use in CompuServe 7.0 and AOL for Mac OS X (these products had previously embedded Internet Explorer). However, with the exception of a few betas, Gecko was never used in the main Microsoft Windows AOL client.{{Citation needed|date=April 2023}}

On July 15, 2003, AOL laid off the remaining Gecko developers and the Mozilla Foundation (formed on the same day) became the main steward of Gecko development. Today, Gecko is developed by employees of the Mozilla Corporation, employees of companies that contribute to the Mozilla project, and volunteers.{{Citation needed|date=April 2023}}

In the Netscape era, a combination of poor technical and management decisions resulted in Gecko software bloat.{{cite web |url = https://arstechnica.com/information-technology/2004/06/collins-interview/2/ |title = Ars Technica sits down with Scott Collins from Mozilla.org |author = Jorge O. Castro |website = Ars Technica |date = 2004-06-15 |access-date=2017-02-16}}{{cite web|url=http://dbaron.org/log/2003-01#l20030109 |archive-url=https://web.archive.org/web/20090728082253/http://dbaron.org/log/2003-01 |title=Thursday 2003-01-09 |work=David Baron's weblog |author=David Baron |publisher=self-published |date=2003-01-09 |archive-date=2009-07-28 |access-date=2017-02-16 |url-status=dead }} Thus in 2001 Apple chose to fork KHTML, not Gecko, to create the WebKit engine for its Safari browser.{{cite web|url=http://news.cnet.com/2100-1023-980492.html |archive-url=https://web.archive.org/web/20121025015655/http://news.cnet.com/2100-1023-980492.html |title=Apple snub stings Mozilla |author=Paul Festa |publisher=CNET Networks |date=2003-01-14 |archive-date=2012-10-25 |access-date=2017-02-16 |author-link=Paul Festa |url-status=dead }} However, by 2008 Mozilla had addressed some of the bloat problems, resulting in significant performance improvements for Gecko.{{cite web |url =https://arstechnica.com/information-technology/2008/09/mozilla-committed-to-gecko/ |author = Ryan Paul |title = Why Mozilla is committed to Gecko as WebKit popularity grows |date = 2008-09-09 |access-date=2017-02-16}}

In October 2016, Mozilla announced Quantum, an ongoing project encompassing several software development efforts to "build the next-generation web engine for Firefox users". It included numerous improvements to Gecko, taken from the experimental Servo project.{{cite web|url=https://wiki.mozilla.org/Quantum|title=Quantum|website=Mozilla Wiki|access-date=2017-04-20}}{{Cite news|url=http://news.softpedia.com/news/mozilla-announces-quantum-a-new-browser-engine-for-firefox-509767.shtml|title=Mozilla Announces Quantum, a New Browser Engine for Firefox|last=Cimpanu|first=Catalin|newspaper=softpedia|access-date=2016-11-07}} Firefox 57, also known as "Firefox Quantum", first shipped in November 2017 and was the initial version with major components from the Quantum/Servo projects enabled. These include increased performance in the CSS and GPU rendering components. Additional components will be merged from Servo to Gecko incrementally in future versions.

In September 2018, Mozilla announced GeckoView, the foundation of Mozilla's next generation of mobile products based on a software library that makes Gecko reusable for Android, encompassing newer software development efforts to "decouple the engine itself from its user interface, and made it easy to embed in other applications". Firefox Focus 7.0, shipped in the same month,{{Cite web|url=https://techdows.com/2018/09/firefox-focus-7-0-to-use-geckoview-gecko-engine.html|title=Firefox Focus 7.0 enters beta, Switches to GeckoView (Gecko Engine)|date=14 September 2018|access-date=19 September 2019|archive-date=31 July 2020|archive-url=https://web.archive.org/web/20200731225124/https://techdows.com/2018/09/firefox-focus-7-0-to-use-geckoview-gecko-engine.html|url-status=dead}} is the initial version introduced GeckoView, with increased performance in median page loading.{{cite web|url=https://hacks.mozilla.org/2018/09/focus-with-geckoview/|title=Firefox Focus with GeckoView|date=September 13, 2018|website=Mozilla Hacks|access-date=September 4, 2019}}{{Cite web|url=https://support.mozilla.org/kb/whats-new-firefox-focus-android-version-7|title=What's new in Firefox Focus for Android (version 7) {{!}} Firefox Focus Help|website=support.mozilla.org|language=en-US|access-date=September 4, 2019}} Firefox Reality was also built with GeckoView. In June 2019, Mozilla announced Firefox Preview as an ongoing project that focuses on building an Android web browser with GeckoView.{{cite web|url=https://hacks.mozilla.org/2019/06/geckoview-in-2019/|title=GeckoView in 2019|date=June 27, 2019|website=Mozilla Hacks|access-date=September 4, 2019}} Firefox for Android 79, also known as "Firefox Daylight", first shipping in August 2020, is the first stable release of that with major components powered by GeckoView engine.{{Cite web|date=August 25, 2020|title=Fast, personalized and private by design on all platforms: introducing a new Firefox for Android experience|author=Vesta Zare|url=https://blog.mozilla.org/blog/2020/08/25/introducing-a-new-firefox-for-android-experience/|access-date=September 22, 2020|website=Mozilla Blog|language=en-US}}

{{Update section|date=August 2022}}

Some of the standards Gecko supports include:

• CSS Level 3
• DOM
• HTML5
• JavaScript (ECMAScript ES6 or superior,{{Cite web |title=Cross Browser Compatibility of ECMAScript 2015 (ES6) in Firefox 102 |url=https://www.lambdatest.com/web-technologies/es6-support-on-firefox-102 |access-date=2022-08-21 |website=www.lambdatest.com |language=en-US |archive-date=2022-08-21 |archive-url=https://web.archive.org/web/20220821071847/https://www.lambdatest.com/web-technologies/es6-support-on-firefox-102 |url-status=dead }} currently ECMAScript 2021 ES12), implemented in SpiderMonkey
• MathML
• RDF
• XForms (via an official extension)
• XHTML 1.0
• XML 1.0
• XSLT and XPath, implemented in TransforMiiX
• SVG{{Cite web |title=Cross Browser Compatibility of SVG (basic support) in Firefox 102 |url=https://www.lambdatest.com/web-technologies/svg-support-on-firefox-102 |archive-url=https://web.archive.org/web/20221209094958/https://www.lambdatest.com/web-technologies/svg-support-on-firefox-102 |url-status=dead |archive-date=December 9, 2022 |access-date=2022-08-21 |website=www.lambdatest.com |language=en-US }}

{{main|Quirks mode}}

In order to support web pages designed for legacy versions of Netscape and Internet Explorer, Gecko supports DOCTYPE switching. Documents with a modern DOCTYPE are rendered in standards compliance mode, which follows the W3C standards strictly. Documents that have no DOCTYPE or an older DOCTYPE are rendered in quirks mode, which emulates some of the non-standard oddities of Netscape Communicator 4.x; however, some of the 4.x features (such as layers) are not supported.

Gecko also has limited support for some non-standard Internet Explorer features, such as the marquee element and the document.all property (though pages explicitly testing for document.all will be told it is not supported).{{cite web |url = http://www.mozillazine.org/talkback.html?article=5063 |title = Mozilla Adds Undetectable document.all Support, Part of New Novell Linux Distribution?|publisher = Developer.mozilla.org |date = 2004-07-23 |access-date = 2018-02-07}}

{{main|Category:Gecko-based software}}

Gecko is primarily used in web browsers, the earliest being Netscape 6 and Mozilla Suite (later renamed SeaMonkey). It is also used in other Mozilla web browser derivatives such as Firefox and Firefox for mobile and the implementation of the Internet Explorer-clone that is part of Wine.{{cite web |url = http://wiki.winehq.org/Gecko |title = IE Uses Gecko Under Wine |publisher = Wine Wiki |access-date = 2009-09-14 }} Mozilla also uses it in their Thunderbird email-client.

Other web browsers using Gecko include LibreWolf, Zen Browser, GNU IceCat,{{Cite web|url=https://www.fsf.org/working-together/gang/gecko|title=Gecko|last=sdubois|date=24 June 2010|website=Free Software Foundation|access-date=23 May 2019}} Midori,{{Cite web |title=Midori Browser light web browser |url=https://astian.org/midori-browser/ |access-date=2025-02-04 |website=Astian, Inc |language=en-US}} Waterfox, K-Meleon, Lunascape, Portable Firefox, Conkeror, Classilla, and TenFourFox.

Gecko is also used by Sugar for the OLPC XO-1 computer,{{Cite news |url=http://www.infoworld.com/article/07/01/03/Hnsugarinterface_1.html |title=One Laptop Per Child readies 'Sugar' interface |last=Martens |first=China |publisher=IDG News Service |date=2007-01-03 |access-date=2007-12-28 |url-status=dead |archive-url=https://web.archive.org/web/20080118115757/http://www.infoworld.com/article/07/01/03/Hnsugarinterface_1.html |archive-date=2008-01-18 }} and is used as a complete implementation of the XUL (XML User Interface Language). Gecko currently defines the XUL specification.{{update inline|date=July 2024|reason=Mozilla discontinued XUL in 2017}} Gecko is also used by the KaiOS mobile operating system, which is based on the discontinued Firefox OS.{{Cite web |url=https://www.neowin.net/news/kaios-technologies-partners-with-mozilla-to-improve-gecko/ |title=KaiOS Technologies partners with Mozilla to improve Gecko |last=Hill |first=Paul |website=Neowin |date=2020-03-12 |access-date=2024-07-12}}

Products that formerly used Gecko include Pale Moon (now using Goanna), Epiphany (now known as GNOME Web and using WebKitGTK), and GNOME DevHelp (now using WebKitGTK).

Discontinued products that used Gecko include Swiftfox, Flock, Galeon, Camino, Minimo, Beonex Communicator, Kazehakase, Songbird, Sunbird (calendar), MicroB, Nightingale, Instantbird, and Picasa for Linux.{{cite web|url=http://picasa.google.com/linux/download.html#picasa30 |title=Picasa 3.0 for Linux |access-date=2008-12-28 |url-status=dead |archive-url=https://web.archive.org/web/20090107022711/http://picasa.google.com./linux/download.html |archive-date=2009-01-07 }}

On Windows and other platforms, Gecko depends on proprietary compilers.{{Cite web|title=Building Firefox for Windows|url=https://firefox-source-docs.mozilla.org/setup/windows_build.html|website=MDN Web Docs}}

After Gecko 2.0, the version number was bumped to 5.0 to match Firefox 5, and from then on has been kept in sync with the major version number for both Firefox and Thunderbird,{{cite web |title = Gecko versions and application versions |url = https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Versions |work = MDN |access-date = 2013-11-18 |archive-date = 2020-10-31 |archive-url = https://web.archive.org/web/20201031145622/https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Versions |url-status = dead }} to reflect the fact that it is no longer a separate component.{{cite web |title = Not much in new Thunderbird 5, but roadmap looks promising |url = https://arstechnica.com/information-technology/2011/06/not-much-in-new-thunderbird-5-but-roadmap-looks-promising/ |website = Ars Technica |date = 30 June 2011 | access-date = 2018-02-07 }}

Quantum is a Mozilla project encompassing several software development efforts to "build the next-generation web engine for Firefox users". It includes numerous improvements to Gecko, largely incorporated from the experimental Servo project. Quantum also includes refinements to the user interface and interactions.

Firefox 57, released in November 2017, is the initial version with a Servo component enabled. Mozilla dubs this and several planned future releases "Firefox Quantum".{{cite web|url=https://www.mozilla.org/en-US/firefox/57.0/releasenotes/|title=Firefox 57.0, See All New Features, Updates and Fixes|website=Mozilla|access-date=2018-10-30}}{{cite web|url=https://blog.mozilla.org/blog/2017/11/14/introducing-firefox-quantum/|title=Introducing the New Firefox: Firefox Quantum – The Mozilla Blog|website=The Mozilla Blog|access-date=2018-10-30}}{{Needs update|date=February 2025|reason=It mentions 2017, so it is somewhat likely the date of the event predicted near this tag has passed.|?=yes}}

In 2012, Mozilla began the experimental Servo project, which is an engine designed from scratch with the goals of improving concurrency and parallelism while also reducing memory safety vulnerabilities. Servo is written in the Rust programming language, also created by Mozilla, which is designed to generate compiled code with better memory safety, concurrency, and parallelism than compiled C++ code.

As of April 2016, Servo needed at least several years of development to become a full-featured browser engine,{{cite web|url=https://github.com/servo/servo/wiki/Remaining-work/0e3b111807c2ed4c11f36d6bd47dda6dfa02d502|title=Servo remaining work|website=GitHub |access-date=2017-02-17}} hence the decision to start the Quantum project to bring stable portions of Servo into Firefox. Mozilla laid off all Servo developers in August 2020.{{Cite web |title=Mozilla lays off 250 employees while it refocuses on commercial products |url=https://www.zdnet.com/article/mozilla-lays-off-250-employees-while-it-refocuses-on-commercial-products/ |access-date=2022-06-14 |website=ZDNet |language=en}}

The Quantum project is composed of several sub-projects.

• CSS: Servo's parallel style sheet system integrated into Gecko. Benchmarks suggest that performance scales linearly with number of CPU cores.{{cite web|url=https://changelog.com/podcast/228|website=The Changelog|title=The Changelog|date=18 November 2016 |access-date=2017-03-28}} This was released in Firefox 57.
• Render: Servo's rendering architecture, called WebRender, integrated into Gecko in 2019, 2 years after the first Firefox Quantum release, Firefox 67. WebRender replaces the immediate mode drawing model with a retained mode model that is more easily accelerated by the GPU by taking advantage of CSS/DOM's similarity to a scene graph. Worst-case scenario rendering in testing exceeds 60 frames per second.{{cite web|url=https://air.mozilla.org/bay-area-rust-meetup-february-2016/|title=Bay Area Rust Meetup February 2016|website=Air Mozilla|access-date=2017-03-28}} Mozilla began enabling the new renderer for select hardware/OS combinations in Firefox 67.{{cite web|url=https://wiki.mozilla.org/Platform/GFX/WebRender_Where|title=Webrender Where|website=Mozilla Wiki|access-date=2020-07-14}}
• Compositor: Gecko's existing compositor moved to its own process, isolating browser tabs from graphics driver related crashes. Since compositor crashes will not bring down the browser content process, the compositor process can be restarted transparently without losing user data. This was released in Firefox 53.{{cite web|url=https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/|title=Firefox faster and more stable with the first big bytes of Project Quantum, simpler with compact themes and permissions redesign|website=Mozilla Blog|access-date=2017-04-27}}
• DOM: Loosely inspired by Servo's Constellation architecture{{cite web|url=https://www.youtube.com/watch?v=an5abNFba4Q |archive-url=https://ghostarchive.org/varchive/youtube/20211211/an5abNFba4Q| archive-date=2021-12-11 |url-status=live|title=Servo Architecture|website=YouTube|date=18 January 2017 |access-date=2017-03-28}}{{cbignore}} and Opera's Presto engine,{{cite web|url=https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/|title=Mozilla's Quantum Project|website=Bill McCloskey's Blog|access-date=2017-03-28|date=2016-10-27}} Quantum DOM uses cooperatively scheduled threads within the DOM to increase responsiveness without increasing the number of processes and, thus, memory usage. The core of this shipped in Firefox 57.{{cite web|url=https://hacks.mozilla.org/2017/11/entering-the-quantum-era-how-firefox-got-fast-again-and-where-its-going-to-get-faster/|title=Entering the Quantum Era|date=2017-11-13|website=Mozilla Hacks|access-date=2020-07-14}}
• Flow: An umbrella for user visible performance improvements driven by a team that works across Gecko components. Focused on real user performance improvements on major webapps, primarily G Suite (now called Google Workspace) and Facebook.{{cite web|url=https://wiki.mozilla.org/Quantum/Flow|title=Quantum Flow|website=Mozilla Wiki|access-date=2017-03-28}} This work completed and shipped for Firefox 57.{{cite web|url=https://ehsanakhgari.org/blog/2017-09-21/quantum-flow-engineering-newsletter-25/|title=Quantum Flow Engineering Newsletter #25|date=2017-09-17|website=ehsanakhgari.org|access-date=2020-07-14}}
• Photon: A UI refresh of the entire application, with a strong focus on improving UI performance. Treated as a sister project to Quantum Flow.{{cite web|url=https://dolske.wordpress.com/2017/05/18/photon-engineering-newsletter-1/|title=Photon Engineering Newsletter #1|last=dolske|date=2017-05-18|website=Dolske's blog|access-date=2017-07-04}} This was released in Firefox 57.
• Network: Improve the performance of Necko, Gecko's networking layer, by moving more network activity off the main thread, context dependent prioritization of networking streams, and racing the cache layer with the network.{{cite web|url=https://wiki.mozilla.org/TPE_Necko/Projects|title=TPE Necko/Projects - MozillaWiki|website=wiki.mozilla.org|access-date=2017-07-04}} This feature was released in Firefox 59.{{cite web|url=https://www.mozilla.org/en-US/firefox/59.0/releasenotes/|title=Firefox 59 Release Notes|website=www.mozilla.org|access-date=2019-01-16}}

The Mozilla Azure project is a stateless low-level graphics abstraction API used in Firefox.{{cite web|url=https://wiki.mozilla.org/Platform/GFX/Moz2D|title=Platform/GFX/Moz2D - MozillaWiki}}

The project has several objectives including:

• more accurate Direct2D compatibility
• optimized state interoperability
• improved control over performance characteristics and bugs

Azure will provide 2D hardware acceleration on top of 3D graphics backends. Firefox began using Azure instead of Cairo in 2012.{{cite web|url=http://news.softpedia.com/news/Firefox-Now-Uses-the-Azure-Graphics-API-for-Canvas-on-All-Platforms-290671.shtml|title=Firefox Now Uses the Azure Graphics API for Canvas on All Platforms|last=Parfeni|first=Lucian|date=7 September 2012 }}{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=OTcxNQ|title=Azure Replacing Cairo In Mozilla Firefox - Phoronix}} It is written in C++ and used by Servo.{{Cite web|url=https://lwn.net/Articles/647969/|title=Parallel page rendering with Mozilla Servo|last1=Willis|first1=Nathan|date=17 June 2015|publisher=LWN.net|access-date=27 June 2015}} The Azure name is an ode to the early Netscape founder James H. Clark and his earlier work at Silicon Graphics where workstations were often named after colors.{{cite web|url=https://blog.mozilla.org/joe/2011/04/26/introducing-the-azure-project/|title=Introducing the Azure project - JOEDREW!|access-date=2019-09-22|archive-url=https://web.archive.org/web/20160908220007/https://blog.mozilla.org/joe/2011/04/26/introducing-the-azure-project/|archive-date=2016-09-08|url-status=dead}}

{{Reflist|30em}}

• [https://developer.mozilla.org/en-US/docs/Glossary/Gecko Gecko - MDN Web Docs]
• [https://wiki.mozilla.org/Gecko:Home_Page Gecko development wiki (wiki.mozilla.org)]
• Quantum Render (wiki.mozilla.org)
• [https://web.archive.org/web/20051126174310/http://cbeard.typepad.com/mozilla/2005/11/mozilla_product.html Mozilla Product Strategy Proposal (DRAFT)]
• [http://www.webdevout.net/browser-support Web Browser Standards Support]
• [http://jrex.mozdev.org/ JRex] {{Webarchive|url=https://web.archive.org/web/20051024022036/http://jrex.mozdev.org/ |date=2005-10-24 }} (Java API for Gecko)

{{Mozilla projects}}

{{Netscape}}

{{Web browser engines}}

{{Web browsers|desktop}}

{{DEFAULTSORT:Gecko (Layout Engine)}}

Category:Cross-platform software

Category:Free layout engines

Category:Free software programmed in C++

Category:Free software programmed in Rust

Category:Mozilla

Category:Software that uses Cairo (graphics)

Category:Netscape