wab brouser ingine
core software component of every major web browser
The name shown is in sco. The article below is in English and is not a translation.
≈ 6 min read
wab brouser ingine. encyclopegia.org, snapshot browser-engine-043286-15c356b08cfb1896. /a/browser-engine
Names in other languages
- Polskisilnik przeglądarki internetowej
- SvenskaRenderingsmotor för webbmaterial
- Češtinarenderovací jádro prohlížeče
- slpogon spletnega brskalnika
- Tiếng Việtđộng cơ trình duyệt webbộ máy trình duyệt web
- camotor de navegador web
- Portuguêsmotor de renderização
- eomotoro de TTT-legilomotoro de retlegilo
- Françaismoteur de rendu HTMLMoteur de rendu de pages web, Moteur de rendu html, Moteur De Rendu HTML, Moteur HTML
- Italianomotore di rendering
- TürkçeWeb tarayıcı motoru
- beрухавічок браўзера
- Españolmotor de navegadormotor de representación
- scowab brouser ingine
- СрпскиWeb browser engine
- azBrauzer mühərriki
- quWamp'uq kuyuchina
- Русскийбраузерный движок
- עבריתמנוע פריסת תצוגה
- Bahasa MelayuEnjin susun atur
- Românămotor de browser
- sqMotor shfletuesi
- Українськабраузерний рушійрушій оглядача
- বাংলাব্রাউজার ইঞ্জিন
- ckbبزوێنەری وێبگەڕ
- ไทยเรนเดอริงเอนจิน
- Englishbrowser enginelayout engine, web layout engine, web rendering engine, rendering engine, web content renderer, web browser engine
- fiselainmoottori
- Bahasa Indonesiamesin perambanmesin tata letak
- 日本語HTMLレンダリングエンジン
- nbnettlesermotor
- DeutschHTML-Renderer
- Magyarböngészőmotor
- ksبراؤزَر اِنجن
- Nederlandslayout-enginerender-engine, rendering engine
- daLayout-motor
- فارسیموتور چیدمان
- اردوبراؤزر انجن
- العربيةمحرك تصميممحرك التصميم
- 한국어브라우저 엔진웹 브라우저 엔진, 렌더링 엔진, 레이아웃 엔진, 웹 레이아웃 엔진, 웹 렌더링 엔진
- 中文浏览器渲染引擎
- 繁體中文網路瀏覽器引擎
- 中文網路瀏覽器引擎
- wuu排版引擎
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
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
edit edit sourceBesides "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
edit edit sourceThe 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
edit edit source- Apple created the WebKit engine for its Safari browser by forking the KHTML engine of the KDE project.[8] Apple mandates that all browsers on App Store for iOS must use WebKit as their engine.[9] (In 2024, the mandate was removed for the European Union and in 2025 for Japan, but it is still enforced elsewhere.[10])
- Google originally used WebKit for its Chrome browser but eventually forked it to create the Blink engine.[11] All Chromium-based browsers use Blink, as do applications built with CEF, Electron, or any other framework that embeds Chromium.
- Microsoft has two proprietary engines, Trident and EdgeHTML. Trident, also called MSHTML, is used in the Internet Explorer browser. EdgeHTML, being a fork of Trident, was the original engine of the Edge browser (now called Edge Legacy); it's still found in some UWP apps.[12] The new, Chromium-based Edge was remade with the Blink engine.[13]
- Mozilla develops the Gecko engine for its Firefox browser and the Thunderbird email client.[2]
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.
See also
edit edit sourceReferences
edit edit source- ^ a b c d "Behind the scenes of modern web browsers". Tali Garsiel. Retrieved 21 April 2018. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ a b "Gecko". Mozilla. Archived from the original on 4 June 2014. Retrieved 21 April 2018. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ "Introducing Goanna". M.C. Straver. 22 June 2015. Retrieved 21 April 2018. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ a b c d "How Blink Works". Retrieved 12 March 2024. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ "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. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Betts, Anaïs (25 October 2016). "Building Hybrid Applications with Electron". Slack Engineering. Slack. Retrieved 1 December 2023. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ 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. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Paul Festa (14 January 2003). "Apple snub stings Mozilla". CNET Networks. Archived from the original on 25 October 2012. Retrieved 16 February 2017. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ "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. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Tim Hardwick (24 October 2024). "iOS 18.2 to Allow Third-Party Browser Web Apps With Custom Engines in EU". MacRumors. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Bright, Peter (3 April 2013). "Google going its way, forking WebKit rendering engine". Ars Technica. Conde Nast. Retrieved 9 March 2017. Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Mendelevich, Alan (14 May 2021). "You Think You Can Forget About the "Legacy" Microsoft Edge? Not So Fast!". Wikipedia revision 1374526332, retrieved 2026-11-21
- ^ Mackie, Kurt (10 December 2018). "Microsoft Edge Browser To Get New Rendering Engine but EdgeHTML Continues". Redmond Mag. Retrieved 21 December 2019. Wikipedia revision 1374526332, retrieved 2026-11-21
Text derived from https://en.wikipedia.org/w/index.php?oldid=1374526332 under CC BY-SA 4.0; modifications have been made.