Jump to content

EdgeHTML: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 39: Line 39:


=== EdgeHTML 12 ===
=== EdgeHTML 12 ===
Microsoft first introduced the EdgeHTML render 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|accessdate=19 November 2015}}</ref> Microsoft planned to use EdgeHTML both in [[Internet Explorer]] and ''Project Spartan'', in Internet Explorer it would exist among 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]]{{dubious|date=November 2015}}, leaving EdgeHTML only for Microsofts 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|accessdate=19 November 2015}}</ref>
Microsoft first introduced the EdgeHTML render 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|accessdate=19 November 2015}}</ref> Microsoft planned to use EdgeHTML both in [[Internet Explorer]] and ''Project Spartan'', in Internet Explorer it would exist among 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|accessdate=6 December 2015}}</ref>, leaving EdgeHTML only for Microsofts 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|accessdate=19 November 2015}}</ref>


Unlike Trident, EdgeHTML doesn't support ActiveX{{disputed|date=November 2015}} and other outdated technologies. 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|accessdate=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 made to improve support with webpages was changing the User Agent String, which claims to be Chrome and Safari, while also using [[KHTML]] and [[Gecko (rendering engine)|Gecko]].
Unlike Trident, EdgeHTML doesn't support ActiveX and other outdated technologies. 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|accessdate=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 made to improve support with webpages was changing the User Agent String, which claims to be Chrome and Safari, while also using [[KHTML]] and [[Gecko (rendering engine)|Gecko]].


{| class="wikitable"
{| class="wikitable"

Revision as of 09:56, 6 December 2015

EdgeHTML
Developer(s)Microsoft
Stable release
13.10586 / 12 November 2015
Preview release
13.10586 / 5 November 2015
Written inC++[1]
TypeApplication framework, software component
LicenseProprietary

EdgeHTML is a proprietary layout engine developed by Microsoft for the Microsoft Edge web browser. It is a fork of Trident that has removed all legacy code of older versions of Internet Explorer and rewritten the majority of its source code with web standards and interoperability with other modern browsers in mind. [2] The rendering engine was first released as an experimental option in Internet Explorer 11 as part of the Windows 10 Technical Preview build 9879.

Usage in Windows

EdgeHTML is designed as a software component to allow software developers to easily add web browsing functionality to their own applications. It presents a COM interface for accessing and editing web pages in any COM-supported environment, like C++ and .NET. For instance, a web browser control can be added to a C++ program and EdgeHTML can then be used to access the page currently displayed in the web browser and retrieve element values. Events from the web browser control can also be captured. It's also used to render WinRT-apps that are based on web technologies.

Release history

EdgeHTML version Edge version Release Notes
12.10240 20.10240 July 15, 2015 Initial release, based on Trident 7.0. Part of Windows since Windows 10 Technical Preview build 10049. Contains improvements to performance, support for HTML5, CSS3 and ECMAScript 6.
13.10586[3] 25.10586 November 5, 2015 First platform update, includes further enhancements to ECMAScript 6 support and HTML5, including Object RTC support.

EdgeHTML 12

Microsoft first introduced the EdgeHTML render engine as part of Internet Explorer 11 in the Windows Technical Preview build 9879 on November 12, 2014.[4] Microsoft planned to use EdgeHTML both in Internet Explorer and Project Spartan, in Internet Explorer it would exist among 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[5], leaving EdgeHTML only for Microsofts 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.[6]

Unlike Trident, EdgeHTML doesn't support ActiveX and other outdated technologies. 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.[7] 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 made to improve support with webpages was changing the User Agent String, which claims to be Chrome and Safari, while also using KHTML and Gecko.

Microsoft EdgeHTML 12 Mozilla/5.0 (Windows NT 10.0;) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240
Internet Explorer 11 Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko

EdgeHTML 13

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. Microsoft also included support for Object RTC and enabled ASM.js by default after it was added in version 12. The update's main focus was on improving the support for ECMAScript 6 and also including some features from ECMAScript 7. With that update to Chakra Edge provided to most extensive support for ECMAScript 6 according to the Kangax benchmark with 84% (and 90% with all flags enabled), 13% ahead of Mozilla Firefox 42, the then-current version of Firefox and runner-up.[3]

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 updated 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.

Performance

A review of the engine in the latest Windows 10 build by AnandTech found substantial benchmark improvements over Trident; particularly JavaScript engine performance, which is now up to par with that of Google Chrome.[8] Other benchmarks focusing on the performance of the WebGL API found EdgeHTML to perform much better than Google Chrome and Mozilla Firefox.[9]

See also

References

  1. ^ Hachamovitch, Dean (2007-12-14), Internet Explorer 8 and Acid2: A Milestone, Microsoft
  2. ^ "What's powering Spartan? Internet Explorer, of course". Neowin.
  3. ^ a b "Introducing EdgeHTML 13, our first platform update for Microsoft Edge". Windows Blog. Retrieved 19 November 2015.
  4. ^ "Living on the edge – our next step in helping the web just work". IE Blog. Retrieved 19 November 2015.
  5. ^ "Updates from the "Project Spartan" Developer Workshop". IE Blog. Retrieved 6 December 2015.
  6. ^ "Windows 10 Free Upgrade Available in 190 Countries Today". Windows Blog. Retrieved 19 November 2015.
  7. ^ "A break from the past: the birth of Microsoft's new web rendering engine". IE Blog. Retrieved 19 November 2015.
  8. ^ Brett Howse. "AnandTech - Internet Explorer Project Spartan Shows Large Performance Gains". anandtech.com.
  9. ^ "Benchmark Deep-Dive: Microsoft Windows 10 Spartan Browser vs. IE11 vs. Google Chrome 41 vs. Mozilla Firefox". WinBuzzer. Retrieved 9 February 2015.

Further reading

Retrieved from "https://en.wikipedia.org/w/index.php?title=EdgeHTML&oldid=693989946"