Jump to content

Gecko (software)

From Wikipedia, the free encyclopedia
(Redirected from Gecko (rendering engine))
Gecko
Developer(s)Mozilla Foundation, Mozilla Corporation, Adobe Systems, and other contributors
Initial release1998 as NGLayout
Stable release
125 / 4 November 2022; 2 years ago (4 November 2022)
Repository
Written inC++, JavaScript, Rust
TypeBrowser engine
LicenseMPL 2.0[1][2]
Websitedeveloper.mozilla.org/en-US/docs/Glossary/Gecko

Gecko (stylized as ɢecko) is a browser engine developed by Mozilla. It is used in the Firefox browser, the Thunderbird email client, and many other projects.

Gecko is designed to support open Internet standards, and is used by different applications to display web pages and, in some cases, an application's user interface itself (by rendering XUL). Gecko offers a rich programming API that makes it suitable for a wide variety of roles in Internet-enabled applications, such as web browsers, content presentation, and client/server.[3]

Gecko is written in C++ and JavaScript,[4][5] and, since 2016, additionally in Rust.[6][7] It is free and open-source software subject to the terms of the Mozilla Public License version 2.[8] Mozilla officially supports its use on Android,[4] Linux, macOS, and Windows.[9]

History

[edit]

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),[10] eventually the Gecko branding won out.[citation needed]

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

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]

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]

In the Netscape era, a combination of poor technical and management decisions resulted in Gecko software bloat.[11][12][13] Thus in 2001 Apple chose to fork KHTML, not Gecko, to create the WebKit engine for its Safari browser.[12][13] However, by 2008 Mozilla had addressed some of the bloat problems, resulting in significant performance improvements for Gecko.[14]

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.[15][16] Firefox 57, also known as "Firefox Quantum", first shipping in November 2017, is 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.[15]

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,[17] is the initial version introduced GeckoView, with increased performance in median page loading.[18][19] Firefox Reality was also built with GeckoView.[18] In June 2019, Mozilla announced Firefox Preview as an ongoing project that focuses on building an Android web browser with GeckoView.[20] 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.[21]

Standards support

[edit]
Related articles
Origins and lineage
Category

From the outset, Gecko was designed to support open Internet standards. Some of the standards Gecko supports include:

Gecko also supports SVG.[23]

Legacy IE non-standard support

[edit]

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).[24]

Usage

[edit]

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.[25] Mozilla also uses it in their Thunderbird email-client.

Other web browsers using Gecko include GNU IceCat,[26] Waterfox, K-Meleon, Lunascape, Portable Firefox, Conkeror, Classilla, TenFourFox.

Gecko is also used by Sugar for the OLPC XO-1 computer,[27] and is used as a complete implementation of the XUL (XML User Interface Language). Gecko currently defines the XUL specification.[needs update] Gecko is also used by the KaiOS mobile operating system, which is based on the discontinued Firefox OS.[28]

Past users

[edit]

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

Proprietary dependency

[edit]

On Windows and other platforms, Gecko depends on proprietary compilers.[30]

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,[31] to reflect the fact that it is no longer a separate component.[32]

Quantum

[edit]

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.[15][16]

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".[33][34]

Background

[edit]

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

As of April 2016, Servo needed at least several years of development to become a full-featured browser engine,[35] 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.[36]

Components

[edit]

The Quantum project is composed of several sub-projects.[15]

  • CSS: Servo's parallel style sheet system integrated into Gecko. Benchmarks suggest that performance scales linearly with number of CPU cores.[37] This was released in Firefox 57.[34]
  • 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.[38] Mozilla began enabling the new renderer for select hardware/OS combinations in Firefox 67.[39]
  • 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.[40]
  • DOM: Loosely inspired by Servo's Constellation architecture[41] and Opera's Presto engine,[42] 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.[43]
  • 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.[44] This work completed and shipped for Firefox 57.[45]
  • Photon: A UI refresh of the entire application, with a strong focus on improving UI performance. Treated as a sister project to Quantum Flow.[46] This was released in Firefox 57.[33]
  • 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.[47] This feature was released in Firefox 59.[48]

Azure

[edit]

The Mozilla Azure project is a stateless low-level graphics abstraction API used in Firefox.[49]
The project has several objectives including:

  • more accurate Direct2D compatibility,
  • optimized state interoperability, and
  • 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.[50][51] It is written in C++ and used by Servo.[52] 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.[53]

References

[edit]
  1. ^ "Mozilla Foundation End-User Licensing Agreements". Mozilla.
  2. ^ "Mozilla Licensing Policies". mozilla.org. Retrieved 2013-03-26.
  3. ^ "Embedding Mozilla". Mozilla.org. 2012-10-25. Retrieved 2012-10-31.
  4. ^ a b "Simple Firefox for Android build". Archived from the original on 2019-09-29. Retrieved 2017-05-03. Gecko is implemented using C++ and JavaScript.
  5. ^ a b Bergstrom, Lars; et al. (May 2016). "Engineering the Servo Web Browser Engine using Rust" (PDF). Proceedings of the International Conference on Software Engineering. Archived (PDF) from the original on 2016-05-29.
  6. ^ "Google Groups". groups.google.com.
  7. ^ Yegulalp, Serdar (February 3, 2017). "Mozilla binds Firefox's fate to the Rust language". InfoWorld.
  8. ^ "MPL 2 Upgrade". Retrieved 2012-08-18.
  9. ^ "Gecko FAQ". MDN Web Docs. Archived from the original on 2019-10-08. Retrieved 2017-05-03.
  10. ^ "nglayout project: identity crisis". Mozilla.org. Archived from the original on 2011-06-29. Retrieved 2012-10-31.
  11. ^ a b Jorge O. Castro (2004-06-15). "Ars Technica sits down with Scott Collins from Mozilla.org". Ars Technica. Retrieved 2017-02-16.
  12. ^ a b Paul Festa (2003-01-14). "Apple snub stings Mozilla". CNET Networks. Archived from the original on 2012-10-25. Retrieved 2017-02-16.
  13. ^ a b David Baron (2003-01-09). "Thursday 2003-01-09". David Baron's weblog. self-published. Archived from the original on 2009-07-28. Retrieved 2017-02-16.
  14. ^ Ryan Paul (2008-09-09). "Why Mozilla is committed to Gecko as WebKit popularity grows". Retrieved 2017-02-16.
  15. ^ a b c d "Quantum". Mozilla Wiki. Retrieved 2017-04-20.
  16. ^ a b Cimpanu, Catalin. "Mozilla Announces Quantum, a New Browser Engine for Firefox". softpedia. Retrieved 2016-11-07.
  17. ^ "Firefox Focus 7.0 enters beta, Switches to GeckoView (Gecko Engine)". 14 September 2018. Archived from the original on 31 July 2020. Retrieved 19 September 2019.
  18. ^ a b "Firefox Focus with GeckoView". Mozilla Hacks. September 13, 2018. Retrieved September 4, 2019.
  19. ^ "What's new in Firefox Focus for Android (version 7) | Firefox Focus Help". support.mozilla.org. Retrieved September 4, 2019.
  20. ^ "GeckoView in 2019". Mozilla Hacks. June 27, 2019. Retrieved September 4, 2019.
  21. ^ Vesta Zare (August 25, 2020). "Fast, personalized and private by design on all platforms: introducing a new Firefox for Android experience". Mozilla Blog. Retrieved September 22, 2020.
  22. ^ "Cross Browser Compatibility of ECMAScript 2015 (ES6) in Firefox 102". www.lambdatest.com. Archived from the original on 2022-08-21. Retrieved 2022-08-21.
  23. ^ "Cross Browser Compatibility of SVG (basic support) in Firefox 102". www.lambdatest.com. Retrieved 2022-08-21.[permanent dead link‍]
  24. ^ "Mozilla Adds Undetectable document.all Support, Part of New Novell Linux Distribution?". Developer.mozilla.org. 2004-07-23. Retrieved 2018-02-07.
  25. ^ "IE Uses Gecko Under Wine". Wine Wiki. Retrieved 2009-09-14.
  26. ^ sdubois (24 June 2010). "Gecko". Free Software Foundation. Retrieved 23 May 2019.
  27. ^ Martens, China (2007-01-03). "One Laptop Per Child readies 'Sugar' interface". IDG News Service. Archived from the original on 2008-01-18. Retrieved 2007-12-28.
  28. ^ Hill, Paul (2020-03-12). "KaiOS Technologies partners with Mozilla to improve Gecko". Neowin. Retrieved 2024-07-12.
  29. ^ "Picasa 3.0 for Linux". Archived from the original on 2009-01-07. Retrieved 2008-12-28.
  30. ^ "Building Firefox for Windows". MDN Web Docs.
  31. ^ "Gecko versions and application versions". MDN. Archived from the original on 2020-10-31. Retrieved 2013-11-18.
  32. ^ "Not much in new Thunderbird 5, but roadmap looks promising". Ars Technica. 30 June 2011. Retrieved 2018-02-07.
  33. ^ a b "Firefox 57.0, See All New Features, Updates and Fixes". Mozilla. Retrieved 2018-10-30.
  34. ^ a b "Introducing the New Firefox: Firefox Quantum – The Mozilla Blog". The Mozilla Blog. Retrieved 2018-10-30.
  35. ^ "Servo remaining work". GitHub. Retrieved 2017-02-17.
  36. ^ "Mozilla lays off 250 employees while it refocuses on commercial products". ZDNet. Retrieved 2022-06-14.
  37. ^ "The Changelog". The Changelog. 18 November 2016. Retrieved 2017-03-28.
  38. ^ "Bay Area Rust Meetup February 2016". Air Mozilla. Retrieved 2017-03-28.
  39. ^ "Webrender Where". Mozilla Wiki. Retrieved 2020-07-14.
  40. ^ "Firefox faster and more stable with the first big bytes of Project Quantum, simpler with compact themes and permissions redesign". Mozilla Blog. Retrieved 2017-04-27.
  41. ^ "Servo Architecture". YouTube. 18 January 2017. Archived from the original on 2021-12-11. Retrieved 2017-03-28.
  42. ^ "Mozilla's Quantum Project". Bill McCloskey's Blog. 2016-10-27. Retrieved 2017-03-28.
  43. ^ "Entering the Quantum Era". Mozilla Hacks. 2017-11-13. Retrieved 2020-07-14.
  44. ^ "Quantum Flow". Mozilla Wiki. Retrieved 2017-03-28.
  45. ^ "Quantum Flow Engineering Newsletter #25". ehsanakhgari.org. 2017-09-17. Retrieved 2020-07-14.
  46. ^ dolske (2017-05-18). "Photon Engineering Newsletter #1". Dolske's blog. Retrieved 2017-07-04.
  47. ^ "TPE Necko/Projects - MozillaWiki". wiki.mozilla.org. Retrieved 2017-07-04.
  48. ^ "Firefox 59 Release Notes". www.mozilla.org. Retrieved 2019-01-16.
  49. ^ "Platform/GFX/Moz2D - MozillaWiki".
  50. ^ Parfeni, Lucian (7 September 2012). "Firefox Now Uses the Azure Graphics API for Canvas on All Platforms".
  51. ^ "Azure Replacing Cairo In Mozilla Firefox - Phoronix".
  52. ^ Willis, Nathan (17 June 2015). "Parallel page rendering with Mozilla Servo". LWN.net. Retrieved 27 June 2015.
  53. ^ "Introducing the Azure project - JOEDREW!". Archived from the original on 2016-09-08. Retrieved 2019-09-22.
[edit]
Retrieved from "https://wiki.riteme.site/w/index.php?title=Gecko_(software)&oldid=1263242877"