4 ms·
They aren't targeting specific sites that are broken they are targeting more general patterns that seem to cause problems.
by Igglyboo 12y ago
They aren't targeting specific sites that are broken they are targeting more general patterns that seem to cause problems.
- leeoniya 12y agoI understand the language. I don't understand what they mean by "patterns". Common edge cases where js/css/html is broken in specific ways? If you write html/css in a relatively compliant way, things will not be so broken that a browser vendor needs to account for them in a "long tail". If your js is broken, well tough luck. Are they just talking about how to implicitly handle commonly malformed HTML, as all browsers do?
- deleted 12y ago[deleted]
- CJefferson 12y agoIf people in the past have written bad js which worked in IE, Microsoft aren't now going to break that code. They don't consider saying "tough luck" to businesses with code which works for them today acceptable.
- leeoniya 12y agomy problem is they're selling this as a "clean break" with no baggage. but then in the same breath explain how they've found a way to still accommodate that baggage and calling it a "long tail". IE is still gonna live next door (to be used for enterprise/compat) probably for a while. I don't understand what they are saying about solving incompatibility issues of IE-specific code in Spartan - which is presumably NOT IE.
- cwyers 12y agoBasically, they took Trident, refactored it and stripped out all the compatibility shims, and made it into EdgeHTML, which they will be working on making similar to WebKit/Blink/Gecko in terms of how it renders web pages. For pages that still need IE, you can switch to Trident, which will still be around.