This may be true, but there are a bunch of useful things IE9 doesn't support that even Firefox 3.6 does:
1. Text shadow
2. Offline applications
3. Multiple column layout
4. Border images
5. Web workers, File API, Geolocation
A lot of these are in the working draft phase, so I can get the "we don't support any feature where the spec is in draft form" argument from IE. But if they want to play a part with the future of the web, IE needs to stop being boring and actually try to implement some draft features and help contribute to developing these standards.
IE needs to stop being boring and actually try to implement some draft features and help contribute to developing these standards.
But the second this happens, I guarantee that people will loudly complain. IE10 comes out with a slew of new features and MS puts them on the docket for standardization. People will say that MS is trying to hijack the web or standards process.
For all the grief MS is getting by being behind, they'd get a lot more grief if they were active and out front w/ respect to features.
Yet, we actually owe many modern web features to Microsoft with IE. There is the obvious stuff, like xmlHttpRequest (Ajax) but also simple stuff like allowing event handlers on every DOM element.
All the stuff that Firefox/Chrome/Safari/Opera are doing now is exactly what IE did for it's entire history up to version 6. And really, IE very quickly became the superior browser of the day. But from then on, they appear to only be putting in minimal effort with no innovation.
1. Text shadow 2. Offline applications 3. Multiple column layout 4. Border images 5. Web workers, File API, Geolocation
A lot of these are in the working draft phase, so I can get the "we don't support any feature where the spec is in draft form" argument from IE. But if they want to play a part with the future of the web, IE needs to stop being boring and actually try to implement some draft features and help contribute to developing these standards.