EdgeHTML: Difference between revisions

Revision as of 04:08, 24 August 2023

Revision as of 10:12, 29 January 2024

Line 30:

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.