4 ms·
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
by 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 agoI don't find the fact a brand new browser already supports legacy 'webkit-' prefixes a fun fact...
- hirsin 12y agoIn 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.