3 ms·
Yet another engine to support. They are creating their own called EdgeHTML
by jastanton 11y ago
Yet another engine to support. They are creating their own called EdgeHTML
- wlesieutre 11y agoIt's replacing Trident for everyone except companies that use internal software designed for IE6, and you can pretty well ignore those users. Same number of engines to support as before.
- davidgerard 11y agoThat's really not how browser support works ... if your customers are paying money, you don't trust a damn thing and you verify stuff on all browsers with any appreciable market share. jastanton is entirely correct.
- wlesieutre 11y agoSure, but IE's rendering engine is probably not going to change appreciably from here on forward, it's just a legacy support thing. If they'd called this IE 12, you'd be supporting IE 8-11 and IE 12. Instead, you're supporting IE 8-11 and Edge. Big difference? Less of a big deal than the Webkit/Blink split, if you ask me.
- davidgerard 11y agoIn my real-life experience, you're simply incorrect here. If all those variants of IE are in use by paying customers (which is our situation), then you do have to account for the fact that they have sufficient individual quirks as to require individual testing. If you don't have paying customers, or you can actually tell them what to browse with, you might plausibly not care. Ours tend to have locked-down desktops and very little personal choice in browser.
- wlesieutre 11y agoYes, you have to test in multiple versions of browsers. My point here is that they are adding one new browser. If they were making a new IE 12 instead of making Edge, you'd be in exactly the same boat of having to test one new browser from Microsoft. Maybe I'm wrong, but I'll be surprised if the version of IE that they ship for enterprise users is practically different from the current version in Windows 8.
- agildehaus 11y agoYou underestimate people's ability to hold on to old software.