EdgeHTML: Difference between revisions

Revision as of 22:08, 29 January 2022

Latest revision as of 11:06, 6 August 2025

(32 intermediate revisions by 22 users not shown)

Line 1:

{{Short description|Former browserBrowser engine of Microsoft Edge (2015–2021)}}

{{Infobox software

| name = EdgeHTML

| logo = File:Microsoft Edge logo.svg

| logo size = 120px

| screenshot = EdgeHTML17ScreenShot.png

| screenshot size = 250px

| caption = [[Microsoft Edge Legacy]], powered by EdgeHTML, displaying a [[Wikipedia]] page in 2018

| developer = [[Microsoft]]

| latest release version = 18.19041

| latest release date = {{Start date and age|2020|05|27}}

| programming language = [[C++]]<ref>{{citation |url=http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx |title=Internet Explorer 8 and Acid2: A Milestone |publisher=Microsoft |first=Dean |last=Hachamovitch |date=2007-12-14}}</ref><!-- look in the file-changelog there are c++ files! -->

| operating system = [[Windows 10]],<br/>[[Windows 10 Mobile]]<br/>[[Xbox system software#Xbox OneSystem andSoftware Xbox Series X/S(2013–present)|Xbox One and Xbox Series X/S system software]]

| replaces = [[MSHTML]]

| replaced_by = [[Blink (browser engine)|Blink]]

Line 17 ⟶ 19:

}}

'''EdgeHTML''' is a [[proprietary software|proprietary]] [[browser engine]] from [[Microsoft]] that was formerly used in [[Microsoft Edge Legacy]], which debuted in 2015 as part of [[Windows 10]].

EdgeHTML is a [[fork (software development)|fork]] of the [[MSHTML]] (Trident) engine of [[Internet Explorer]].<ref>{{cite web|url=http://www.neowin.net/news/whats-powering-spartan-internet-explorer-of-course|title=What's powering Spartan? Internet Explorer, of course|work=[[Neowin]]|date=24 August 2023 }}</ref> It is designed as a [[Component-based software engineering|software component]] that enables [[software developer|developers]] to easily to add web browsing functionality to other [[application software|apps]].<ref>{{Cite web|last=Mackie|first=Kurt|date=10 December 2018|title=Microsoft Edge Browser To Get New Rendering Engine but EdgeHTML Continues|url=https://redmondmag.com/articles/2018/12/10/edgehtml-continues.aspx|access-date=2021-02-13|website=Redmondmag}}</ref>

In 2018, Microsoft began rebuilding Edge as a [[Chromium (web browser)|Chromium]]-based browser,<ref>{{citation |url=https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration |title=Microsoft Edge: Making the web better through more open source collaboration |publisher=[[Microsoft]] |first=Joe |last=Belfiore |date=2018-12-06}}</ref><ref>{{cite web |url=https://github.com/MicrosoftEdge/MSEdge/blob/7d69268e85e198cee1c2b452d888ac5b9e5995ca/README.md |title=Microsoft Edge and Chromium Open Source: Our Intent |date=6 December 2018 |publisher=Microsoft Edge Team |access-date=8 December 2018}}</ref> which meant that EdgeHTML would no longer be used in the Edge browser. This transition was completed in April 2021.<ref>{{Cite web|title=Microsoft will uninstall its old Edge browser from Windows PCs on April 13th|url=https://www.engadget.com/microsoft-edge-legacy-phase-out-232116614.html|access-date=2021-11-24|website=[[Engadget]]}}</ref> Past this date, EdgeHTML does, however, continue to be supported and widely used in [[UWPUniversal Windows Platform apps]].<ref>{{citation|url=https://blog.ailon.org/you-think-you-can-forget-about-the-legacy-microsoft-edge-not-so-fast-28ce91270a22|title=You Think You Can Forget About the “Legacy”"Legacy" Microsoft Edge? Not So Fast!|publisher=[[Medium (website)|Medium]]|first=Alan|last=Mendelevich|date=2021-05-14}}</ref>

== History ==

Microsoft first introduced the EdgeHTML rendering engine as part of [[Internet Explorer 11]] in the Windows Technical Preview build 9879 on November 12, 2014.<ref>{{cite web|title=Living on the edge – our next step in helping the web just work|url=http://blogs.msdn.com/b/ie/archive/2014/11/11/living-on-the-edge-our-next-step-in-interoperability.aspx|website=IE Blog|access-date=19 November 2015}}</ref> Microsoft planned to use EdgeHTML both in [[Internet Explorer]] and ''Project Spartan''; in Internet Explorer it would exist alongside the Trident 7 engine from Internet Explorer 11, the latter being used for compatibility purposes. However, Microsoft decided to ship Internet Explorer 11 in [[Windows 10]] as it was in [[Windows 8.1]],<ref>{{cite web|title=Updates from the "Project Spartan" Developer Workshop|url=http://blogs.msdn.com/b/ie/archive/2015/03/24/updates-from-the-project-spartan-developer-workshop.aspx|website=IE Blog|access-date=6 December 2015}}</ref> leaving EdgeHTML only for the then new Edge [Legacy] browser. EdgeHTML was also added to [[Windows 10 Mobile]] and the second [[Windows Server 2016]] Technical Preview. It was officially released on July 29, 2015, as part of Windows 10.<ref>{{cite web|title=Windows 10 Free Upgrade Available in 190 Countries Today|url=http://blogs.windows.com/windowsexperience/2015/07/28/windows-10-free-upgrade-available-in-190-countries-today/|website=Windows Blog|date=29 July 2015 |access-date=19 November 2015}}</ref>

Unlike Trident, EdgeHTML does not support [[ActiveX]]. It also drops support for the X-UA-Compatible header, used by Trident to determine in which version it had to render a certain page. Microsoft also dropped the usage of Compatibility View-lists.<ref>{{cite web|title=A break from the past: the birth of Microsoft's new web rendering engine|url=http://blogs.msdn.com/b/ie/archive/2015/02/26/a-break-from-the-past-the-birth-of-microsoft-s-new-web-rendering-engine.aspx|website=IE Blog|access-date=19 November 2015}}</ref> Edge will recognize if a page requires any of the removed technologies to run properly and suggest to the user to open the page in Internet Explorer instead. Another change was spoofing the [[user agent string]], which claims to be Chrome and [[Safari (web browser)|Safari]], while also mentioning [[KHTML]] and [[Gecko (rendering engine)|Gecko]], so that web servers that use user agent sniffing send Edge users the full versions of web pages instead of reduced-functionality pages.

EdgeHTML's rendering was meant to be fully compatible with the rendering of the [[Blink (web engine)|Blink]] and [[WebKit]] layout engines, used by [[Google Chrome]] and [[Safari (web browser)|Safari]], respectively. At the time, Microsoft stated that "any Edge-WebKit differences are bugs that we’re interested in fixing."<ref>{{cite web|url=https://blogs.windows.com/msedgedev/2015/06/17/building-a-more-interoperable-web-with-microsoft-edge/|title=Building a more interoperable Web with Microsoft Edge|date=17 June 2015 }}</ref>

Breaking from Trident, the new EdgeHTML engine will bewas focused on modern web standards and interoperability, rather than compatibility. The initial release of EdgeHTML on Windows 10 included more than 4000 interoperability fixes.<ref>{{cite web|author1=Microsoft Edge Team|title=Building a more interoperable Web with Microsoft Edge|url=https://blogs.windows.com/msedgedev/2015/06/17/building-a-more-interoperable-web-with-microsoft-edge/|website=Microsoft Edge Dev Blog|access-date=8 May 2016|language=en-US|date=17 June 2015}}</ref>

On August 18, 2015, Microsoft released the first preview to EdgeHTML platform version 13 as part of Windows 10.0.10525, though it was still labeled as version 12. In subsequent updates, the support for HTML5 and CSS3 was extended to include new elements.

EdgeHTML 13.10586 was released in multiple versions of Windows. On November 12, 2015, the ''New [[Xbox One]] Experience''-update for the Xbox One included EdgeHTML 13.10586, replacing [[Internet Explorer 10]] in the process. It was released to [[Windows 10]] as part of the November Update on the same day. On November 18, 2015, the updatedupdate got rolled out to Windows 10 Mobile users in the Insider Preview. Finally, Microsoft rolled out the same update to [[Windows Server 2016]] as part of Technical Preview 4.

On December 16, 2015, Microsoft released the first build of ''Redstone''. In January and February 2016, 4 other builds followed, all laying the foundational work for EdgeHTML 14. On February 18, 2016, Microsoft released the first version of EdgeHTML 14 as version 14.14267. This version of the engine contained almost no changes in standards support yet, but contained fundamental work for [[Web Notification]]s, [[WebRTC 1.0]], improved [[ECMAScript]] and CSS support and also contained a number of new flags.<ref>{{cite web |last1=Gupta |first1=Prateek |title=Best Microsoft Edge Flags |url=https://gizmeek.com/best-microsoft-edge-flags |website=GizMeek|date=26 September 2020 }}</ref> Further, Microsoft announced that it was working on [[VP9]], [[WOFF 2.0]], [[Web Speech API]], [[WebM]], [[FIDO 2.0]], and [[Beacon API]].

EdgeHTML has often been compared to [[Gecko (software)|Gecko]] due to its standards support and lack of compatibility with WebKit.<ref>{{Cite web |last=jasonrmns |date=2018-12-04 |title=Gecko is the last engine standing: Microsoft is scrapping EdgeHTML for Chromium |url=http://www.reddit.com/r/firefox/comments/a2wfx8/gecko_is_the_last_engine_standing_microsoft_is/ |access-date=2023-07-16 |website=r/firefox}}</ref>

===Releases===

Line 79 ⟶ 83:

|13.10586

|November 5, 2015

|First public platform update, includes further enhancements to HTML5, including Object RTC support.<ref name=edgehtml-13>{{cite web|title=Introducing EdgeHTML 13, our first platform update for Microsoft Edge|url=https://blogs.windows.com/msedgedev/2015/11/16/introducing-edgehtml-13-our-first-platform-update-for-microsoft-edge/|website=Windows Blog|date=16 November 2015|access-date=19 November 2015}}{{Dead link|date=August 2025 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>

|-

|13.11099

Line 107 ⟶ 111:

|14.14342

|May 10, 2016

|Web Notifications, Beacon, and Fetch APIs became enabled by default, Performance improvements for several common JavaScript APIs.

|-

|14.14352

Line 208 ⟶ 212:

[[Category:Internet Explorer]]

[[Category:LayoutBrowser engines]]

[[Category:Microsoft Edge]]

[[Category:Windows web browsers]]