Linked by Adam S on Wed 5th Apr 2006 12:52 UTC, submitted by estherschindler
DevSource's John Mueller has an excellent "first look" at what it will take for Web developers to make their apps work with IE7. He says, "Unless you're using pretty much pure HTML on static pages, your application is going to break in some way."
Thread beginning with comment 111701
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2005-11-14
I just hope IE7 final is much much better than the steaming pile of crap that is IE7 beta2.
According to Gates in Vegas last month, IE7 beta2 represents the final renderer for IE7. The number of things it improved (compared to most previous updates, even incremental ones) is pathetic.
Some CSS box model calculations were fixed, + and > CSS operators are supported, and that's about it. No support for a single CSS2 property that wasn't supported in IE6, and that means about half of the spec.
It's a turd for tards.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
As long as they're actually moving IE towards w3c standards -- good. Obviously they're not going to make a huge move towards standards right away, at the risk of truly breaking almost every site out there, so hopefully they are actually committed to gradually moving towards w3c standards.
Though I'm a bit worried that they're only going to go so far, as they tend to not like to make a product like IE a "moving target", meaning something that is constantly changing and site developers can't depend on certain rendering things to work a certain way, as is the case with FF and Opera for the most part. As MS puts it themselves, a "stable platform."
I just hope IE7 final is much much better than the steaming pile of crap that is IE7 beta2. Not that I will use it anymore than I have to (for work) even if it was good.