4 ms·
How does taking advantage of standards-compliant layouts requiring breaking the past? I mean, if they're truly standards-compliant layouts, then they shouldn't
by narcissus 13y ago
How does taking advantage of standards-compliant layouts requiring breaking the past?
I mean, if they're truly standards-compliant layouts, then they shouldn't be doing anything that requires that old stuff, and therefore they shouldn't be affected whether that stuff stays in or not. Or maybe I'm missing something.
Don't get me wrong, it sounds like it's headed in the right direction, but to me, at least, it's more about forcing crappy older sites to update their stuff than anything else.
- ax 13y agoThis is explicitly about getting more sites to work /without/ forcing older sites to update their stuff. Older sites have ifIE() checks that return true and serve IE old legacy IE-specific code. IE11 is more compatible with standards-compliant code than legacy IE-specific code so forcing existing sites to serve IE the same code as FF/Chrome results in more sites working in IE.
- ajross 13y agoYou're missing the point. If they're truly standards-compliant and they "look like" IE6, then they'll get the IE6 layout the site author added and miss out on the new features. So IE11 will look bad and crufty no matter how good it's engine is. The point here is to make it "Look like WebKit" or "Look like Gecko", so that site designers don't try to support old IE versions.