[2] It is designed as a software component that enables developers easily to add web browsing functionality to other apps.

[6] Past this date, EdgeHTML does, however, continue to be supported and used in Universal Windows Platform apps.

[7] Microsoft first introduced the EdgeHTML rendering engine as part of Internet Explorer 11 in the Windows Technical Preview build 9879 on November 12, 2014.

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.

"[12] Breaking from Trident, the new EdgeHTML engine was focused on modern web standards and interoperability, rather than compatibility.

Finally, Microsoft rolled out the same update to Windows Server 2016 as part of Technical Preview 4.

EdgeHTML has often been compared to Gecko due to its standards support and lack of compatibility with WebKit.