Content deleted Content added
No edit summary |
No edit summary |
||
Line 23:
== 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 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|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.
Line 29:
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}}</ref>
Breaking from Trident, the new EdgeHTML engine will be focused on modern web standards and interoperability, rather than compatibility. The initial release of
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.
| |||