Win10 Spartan browser and IE completely draw a line

Computer store news: For the Windows 10 Spartan browser being prepared, Microsoft hopes that the Edge rendering engine used by Sparta can have a "new start", completely disconnecting it from IE. ; veteran level & rdquo; engine Trident's contact.

Jacob Rossi, a senior engineer on the Microsoft Web Platform team, published a tech article on the Edge engine on Smashing Magazine. He said that the current IE11 browser supports many current web standards, but its Trident engine also enables IE11 to browse older websites with older web standards. The web platform team hopes that the Edge engine can use IE11's modern web support standards without having to bear the burden of old-fashioned standards.

Senior engineer Jacob Rossi said:

In the next few months, the shackles left in IE will not appear in new engines. IE's Document modes compatibility model will no longer exist. The subsystem that simulates the IE8 layout and the scripting language VBScript will also be removed. Residues such as attachEvent, X-UA-Compatible and currentStyle will disappear from the new engine. The code for the new engine is no longer similar to Trident (even bigger than Blink's relative to WebKit).

The new and old generations of rendering engines will completely draw a line. A modern web browsing platform will be built to the standards of interoperability and new kernels. From this perspective, we have begun to increase R&D investment in interoperability with other current browsers in order to ensure that developers can achieve a smooth transition across browser development.

Currently, the Spartan browser has not been added to Windows 10 Build 9926, but its new Edge rendering engine can be launched via IE. But are old-fashioned web sites likely to be incompatible with Spartan and Edge?

Senior engineer Jacob Rossi wrote:

IE will still appear in Windows 10, designed for some Support for enterprise web applications that require higher backward compatibility. This version of IE will use the same dual-engine solution as the Spartan EdgeHTML engine, which means developers don't need to differentiate between IE and Sparta, and our standard roadmap will remain the same.