3 ms·

IE11 trident rendering engine was already renamed to "Edge", press F12 check it out (then see in the bottom bar -> top right). The step from IE11 to IE12 aka Ed

by frik 12y ago

IE11 trident rendering engine was already renamed to "Edge", press F12 check it out (then see in the bottom bar -> top right). The step from IE11 to IE12 aka Edge from the render engine is not as huge an outside might think (reading only the PR) - it's still a great step forward so don't get me wrong. The GUI window app has been completely scrapped in favor of a WinRuntime app "Edge" instead of the old iexplore.exe that code can be traced back to at least Internet Explorer 3 (and maybe even IE 1).

hirsin 12y ago
Partially correct. EdgeHTML was in IE11, but wasn't a renamed MSHTML (check your system32, you'll see both DLLs in Win10). It's a departure from MSHTML that's been seriously changed, lots of cruft removed and a lot of interop added. Fun anecdote - last week someone at Steam wrote one of the sale pages using entirely -webkit- prefixes. It showed up blank in Forefox, but rendered fine in Spartan and Chrome.
- Offler 12y ago
  I don't find the fact a brand new browser already supports legacy 'webkit-' prefixes a fun fact...
  - hirsin 12y ago
    In truth, neither do I. But Edge/Spartan follows the developers, and sometimes that involves being interoperable with poorly designed sites that have fallen prey to browser-specific prefixes. From a business sense, it works because if it works in Chrome and fails in Spartan, it's our fault. From a user experience sense, it also works because they deserve to have their sites work.