To read all comments associated with this story, please click here.
You beat me to it!
I stopped making special provisions for IE LONG ago. Every time I write a site it works in all browsers without issue... then I cringe when I see what IE does with it...
My CSS for ALL non-IE browsers will look like:
#myElement {
display: block;
margin: auto;
opacity: 0.85;
}
In order to work with IE8 I have to add:
If I want IE7 support:
And if I want IE6:
And that is just the beginning of the crap...
--The loon
Not quite. While they're not perfect, most of the compatibility issues I've seen in IE9 and 10 have been because of all the workarounds that people had to write for previous versions - as IE becomes more standards compliant, those workarounds start causing problems instead of fixing them.
I agree. That's why they were heavily advocating feature detection (http://blogs.msdn.com/b/ie/archive/2010/04/14/same-markup-writing-c...) instead of browser detection.
Normally frameworks like jQuery are supposed to solve this problem, however many web "so called" developers still use <IF IE> like constructs as a shortcut to real engineering.
iOS didn't (still doesn't, and very likely will not) support Flash, everyone complained "so how do I watch videos on blah blah blah website!?", "how do I play Flash games blah blah blah!?". Few years later, Adobe announced that Flash player for Android 4.x (?) will be the last version and no more further development will be done. Everyone rejoice "whoa! yeah! bye bye Flash! no more power consumption monster!".
But how people react to the blocking policy of Flash content on IE? Before: "oh god I NEED FLASH to live! add ALL sites to the damn whitelist!" After: "heh, MSFT is trying to save face!"
People, do you really know what do you want? If you want to move away from Flash/ add-on world, then it is necessary to rewrite websites which make use of Flash/ other technologies rely on add-on, and you will have a native (HTML5/ JavaScript), faster and perhaps less power consuming implementation. Otherwise, keep using Flash, but don't, I mean DO NOT, complain a device/ browser is consuming your precious battery power or exposing another interface for attacks.
To me, MSFT changes the policy because (1) there are too many average joe who doesn't know Flash has many drawbacks (power consumption, security, etc.) and (2) there are tons of web developers who are too lazy to move away from Flash. I haven't check the blacklist in the update, but I would suggest put every website that has HTML5 version in the blacklist, so that it forces developers (and users?) to realize that there is a better implementation.
Content providers will have to update their content for iOS based devices and modern Android hw anyway. Microsoft just pu**ied out and did the wrong thing. You can always count on MS to do the wrong thing.





Member since:
2006-03-20
Microsoft say the change is due to "more sites becoming IE10 compatiblemore sites becoming IE10 compatible".
The arrogance!
It's IE10 that needs to be compatible with websites that work fine with every other browser .. we don't want the 90's browser hell all over again...