3 ms·
Not only do MS's figures show their tests they they created (so that 100% means they met a self-defined project goal not that they match 100% of any externally
by dspillett 16y ago
Not only do MS's figures show their tests they they created (so that 100% means they met a self-defined project goal not that they match 100% of any externally defined/agreed standard), they don't entirely compare like for like. While they show how bad IE8 is compared to the other currently released competition, they list there own "won't be released for a couple of months yet" version but don't include other people's alpha/beta/RC versions.
It would be interesting to see how well FF4 and the current Opera and Chrome pre-releases manage against this set of tests (probably not 100% as the tests have a built-in bias, but I'm sure they'd do better.
- kenjackson 16y agoAll the tests have been given to the W3C. Once they've been added to the test suite, you'll be able to compare them to whatever browser you like, whever you like. The current W3C suite is here: http://test.w3.org/html/tests/reporting/report.htm http://test.w3.org/html/tests/reporting/report.htm More tests need to be added. If you have some tests, please submit. Please help to make this suite robust. Otherwise its just inactive complaining.
- dspillett 16y agoThere are already other tests though, but MS didn't use them in this analysis. Hence it is a good test to see if they've reached there project goal but not a good test of general compatibility with the standards. If they are just using their own tests and not the others, then raising more test cases is not going to make any difference.