51–52 of 52 posts
Will we have to do this from now on?
no, because there are no document modes, and therefore no x-ua-compat modes
1. something said or done to provoke laughter or cause amusement, as a witticism, a short and amusing anecdote
2. (as verb) to speak or act in a playful or merry way
3. (as verb) to say something in fun or teasing rather than in earnest; be facetious
Earlier quoted context omitted.
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.
I don't find the fact a brand new browser already supports legacy 'webkit-' prefixes a fun fact...
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.