This is a very carefully selected set of test cases that only cover a small subset of HTML5. For example, most of their CSS test cases focus on border-radius (mostly obscure corner cases), but what about shadows, gradients, independent transparency, etc? I appreciate Microsoft's efforts to support HTML5 in their next release of IE but this page is simply ridiculous.
It seems like they picked a few features of HTML5 and decided to support only those but support them well down to the most obscure corner cases, as opposed to the "let's do everything now and then we will fix it later if it's not working properly" approach of open source browsers.
The main problem is that IE release cycle is considerably slower than other browsers'. If they only implement a few features, we have to wait several years to other features, if they implemented all features, we would have to wait several years for Microsoft to fix the bugs. The web these days is just too fast paced for that. It would be a lot better if they switched to a more frequent release cycle.
So the countermove is for other browser vendors to go through the list and fix these "small" cases. This takes away any of IE9's bragging rights and we'll have 5 browsers that pass on this exact subset of tests. Microsoft is forced to be more compatible and html5 arrives on the scene sooner. IE9 takes us to 2014 or 2015. Let's push Microsoft to do even better.
Release cycles matter: just randomly clicking through the tests, most of the reported failures for Safari or Chrome already work using WebKit or Chromium dev channel - both of which are likely to make it into official releases before IE9 comes out.
Comments
This is a very carefully selected set of test cases that only cover a small subset of HTML5. For example, most of their CSS test cases focus on border-radius (mostly obscure corner cases), but what about shadows, gradients, independent transparency, etc? I appreciate Microsoft's efforts to support HTML5 in their next release of IE but this page is simply ridiculous.
It seems like they picked a few features of HTML5 and decided to support only those but support them well down to the most obscure corner cases, as opposed to the "let's do everything now and then we will fix it later if it's not working properly" approach of open source browsers.
The main problem is that IE release cycle is considerably slower than other browsers'. If they only implement a few features, we have to wait several years to other features, if they implemented all features, we would have to wait several years for Microsoft to fix the bugs. The web these days is just too fast paced for that. It would be a lot better if they switched to a more frequent release cycle.
So the countermove is for other browser vendors to go through the list and fix these "small" cases. This takes away any of IE9's bragging rights and we'll have 5 browsers that pass on this exact subset of tests. Microsoft is forced to be more compatible and html5 arrives on the scene sooner. IE9 takes us to 2014 or 2015. Let's push Microsoft to do even better.
It won't matter. For them to have constructed such a biased test shows how much in denial they are. It's pretty depressing actually.
Release cycles matter: just randomly clicking through the tests, most of the reported failures for Safari or Chrome already work using WebKit or Chromium dev channel - both of which are likely to make it into official releases before IE9 comes out.
Here's a response to the web browser tests recently performed on the Internet Explorer Testing Center:
http://www.freeciv.net/yet-another-html5-browser-test/