Browser engine

From Wikipedia, the free encyclopedia

Template:Short description Script error: No such module "Distinguish". Template:DMCA

A browser engine (also known as a layout engine or rendering engine) is a core software component of every major web browser. The primary job of a browser engine is to transform HTML documents and other resources of a web page into an interactive visual representation on a user's device.

Name and scope

Besides "browser engine", two other related terms are commonly used: "layout engine" and "rendering engine".[1][2][3] In theory, layout and rendering (or "painting") could be handled by different engines. In practice, however, these components are tightly coupled and rarely encountered on their own outside of the browser engine.[1][4]

In addition to layout and rendering, a browser engine enforces the security policy between documents, handles navigation through hyperlinks and data submitted through forms, and implements the document object model (DOM) exposed to scripts associated with the document.[1][4]

To provide a wide range of dynamic behavior for web pages, every major browser supports JavaScript. However, JavaScript is implemented as a separate JavaScript engine, which has enabled its usage elsewhere. In a browser, the two engines are coordinated via the DOM and Web IDL bindings.[4]

Browser engines are also used in non-browser applications. An email client needs one to display HTML email. Beginning in the 2010s, many apps have been created with the frameworks based on Google's Chromium project; each of these standalone apps functions much like a web app. (Two examples are Spotify and Slack.)[5][6]

Layout and rendering

The layout of a web page is typically specified by Cascading Style Sheets (CSS). Each style sheet is a series of rules for how the page should be presented. For example, some rules specify typography details, such as font, color, and text size, while others determine the placement of images. The engine combines all relevant CSS rules to calculate precise graphical coordinates and pixel values for the visual representation it will paint on the screen.[1][4]

The engine updates the visual representation in response to new events, including the user scrolling the page, content being asynchronously fetched, video playback, and canvas animations. It also may begin rendering before a page's resources are downloaded, which can result in visual changes as more data is received, such as images being gradually filled in or a flash of unstyled content.[7]

Notable engines

Script error: No such module "labelled list hatnote".

The following chart shows the duration of active development (when relevant new web standards continue to be added) for each engine in this section. Note that Gecko, WebKit, and Blink are still actively developed.

<timeline>

  1. header

ImageSize = width:750 height:170 PlotArea = left:80 right:5 bottom:20 top:5 AlignBars = justify DateFormat = dd/mm/yyyy Period = from:01/01/1997 till:31/05/2022 TimeAxis = orientation:horizontal format:yyyy

Colors =

 id:microsoft     value:rgb(0.3, 0.5, 1)
 id:gecko       value:rgb(1, 0, 0)
 id:khtml       value:rgb(0.3,0.3,0.3)
 id:webkit      value:rgb(0.3, 0.36, 0.36)
 id:blink       value:rgb(0.3, 0.39, 0.39)
 id:mgray       value:rgb(0.5, 0.5, 0.5)
 id:lgray       value:rgb(0.75, 0.75, 0.75)

ScaleMajor = gridcolor:mgray unit:year increment:1 start:01/01/1997 ScaleMinor = unit:month increment:3 start:01/01/1997 BackgroundColors = bars:lgray

BarData =

 bar:Gecko           text:Gecko
 bar:Trident          text:Trident
 bar:EdgeHTML        text:EdgeHTML
 bar:KHTML           text:KHTML
 bar:WebKit          text:WebKit
 bar:Blink           text:Blink

PlotData=

 align:center textcolor:black fontsize:8 mark:(line,black) width:15 shift:(0,-4)
 bar:Gecko
 from: 01/05/1997  till: 31/05/2022    color:gecko mark:(line,white)
 bar:Trident
 from: 01/10/1997  till: 15/07/2015    color:microsoft mark:(line,white)
 bar:EdgeHTML
 from: 12/11/2014  till: 15/12/2018    color:microsoft mark:(line,white)
 bar:KHTML
 from: 04/11/1998  till: 15/10/2016    color:khtml mark:(line,white)
 bar:WebKit
 from: 25/06/2001  till: 31/05/2022    color:webkit mark:(line,white)
 bar:Blink
 from: 03/04/2013  till: 31/05/2022    color:blink mark:(line,white)

</timeline>

See also

References

Page Template:Reflist/styles.css has no content.

  1. ^ a b c d Page Module:Citation/CS1/styles.css has no content."Behind the scenes of modern web browsers". Tali Garsiel. Retrieved 21 April 2018.
  2. ^ a b Page Module:Citation/CS1/styles.css has no content."Gecko". Mozilla. Archived from the original on 4 June 2014. Retrieved 21 April 2018.
  3. ^ Page Module:Citation/CS1/styles.css has no content."Introducing Goanna". M.C. Straver. 22 June 2015. Retrieved 21 April 2018.
  4. ^ a b c d Page Module:Citation/CS1/styles.css has no content."How Blink Works". Retrieved 12 March 2024.
  5. ^ Page Module:Citation/CS1/styles.css has no content."Open Source - Spotify". Retrieved 1 December 2023. Here are the sources to the great Chromium Embedded Framework that is used by the Spotify Desktop client.
  6. ^ Page Module:Citation/CS1/styles.css has no content.Betts, Anaïs (25 October 2016). "Building Hybrid Applications with Electron". Slack Engineering. Slack. Retrieved 1 December 2023.
  7. ^ Page Module:Citation/CS1/styles.css has no content.Boudreaux, Ryan (18 October 2013). "How to prevent Flash of Unstyled Content on your websites". TechRepublic. Archived from the original on 5 March 2021. Retrieved 9 October 2021.
  8. ^ Page Module:Citation/CS1/styles.css has no content.Paul Festa (14 January 2003). "Apple snub stings Mozilla". CNET Networks. Archived from the original on 25 October 2012. Retrieved 16 February 2017.
  9. ^ Page Module:Citation/CS1/styles.css has no content."Open-sourcing Chrome on iOS!". 2017. Retrieved 26 April 2021. Due to constraints of the iOS platform, all browsers must be built on top of the WebKit rendering engine.
  10. ^ Page Module:Citation/CS1/styles.css has no content.Tim Hardwick (24 October 2024). "iOS 18.2 to Allow Third-Party Browser Web Apps With Custom Engines in EU". MacRumors.
  11. ^ Page Module:Citation/CS1/styles.css has no content.Bright, Peter (3 April 2013). "Google going its way, forking WebKit rendering engine". Ars Technica. Conde Nast. Retrieved 9 March 2017.
  12. ^ Page Module:Citation/CS1/styles.css has no content.Mendelevich, Alan (14 May 2021). "You Think You Can Forget About the "Legacy" Microsoft Edge? Not So Fast!".
  13. ^ Page Module:Citation/CS1/styles.css has no content.Mackie, Kurt (10 December 2018). "Microsoft Edge Browser To Get New Rendering Engine but EdgeHTML Continues". Redmond Mag. Retrieved 21 December 2019.

Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.