Developers › A Journal from Behind the Trenches
Is Internet Explorer 9 the most HTML5 compliant browser? Not quite.
PC World, for example, writes:
This would be quite amazing if it was true. But it isn't. You can't draw such conclusions based on those tests.Internet Explorer 9 has topped all other browsers in conforming with the HTML5 specification, including Google Chrome and Firefox, according to tests carried out by the World Wide Web Consortium.
Webmonkey gets it right:
The article is a recommended read for anyone who wants to understand what's actually going on here. Unfortunately, they are referring to the flawed html5test.com site (which doesn't test just HTML5, and which uses a strange way to assign scores), but that's a different story... Do read the article if you want to learn more about the test that is claimed to declare IE9 as the HTML5 leader.The reason IE9 tops the W3C’s list is that the test looks at only a fraction of the HTML5 spec. In other words, the test is very limited. Even better, it’s limited to things IE9 is good at.
There are also some comments from various browser vendors on the HTML test suite mailing list on the subject. For example, there seem to be bugs that affect the pass percentages, and the results for Opera are reportedly "partly bogus".
Needless to say, "IE9 wins at HTML5" is now all over the web. Unfortunately, I doubt that most of the articles that declare IE9 the "winner" are going to be updated to reflect the reality of the situation.
Yet another major PR win for Microsoft, then.
Readers' comments 19
Left under the original article, as archived.
About this article
| Published in | A Journal from Behind the Trenches |
|---|---|
| Date | November 2, 2010 |
| Author | Haavard |
| Tags | html5, press, misleading, w3c, open standards, marketing, microsoft |
| Original | Internet Archive |
lucideerTuesday, November 2, 2010 9:53:09 PM
Charles SchlossTuesday, November 2, 2010 10:18:04 PM
I wonder how much they paid
Rafael LuikTuesday, November 2, 2010 10:20:32 PM
Now a post about Skyfire??
(
http://twitter.com/opvard/status/21475364630
http://twitter.com/opvard/status/21537960372
http://twitter.com/opvard/status/21537224294
http://twitter.com/opvard/status/22736373000
http://twitter.com/opvard/status/29480312603
)
SeldaekTuesday, November 2, 2010 10:22:10 PM
So it's not like you (Opera) and the other browser vendors didn't see it coming. The test suite is a plus for interoperability in the grand scale of things, if you look beyond the PR noise, and I hope every vendor will contribute/keep contributing.
HaavardTuesday, November 2, 2010 10:37:27 PM
Originally posted by rafaelluik:
I have tried to reason with them (including their CEO). There is no getting through to them. I think attention is exactly what they are after.Originally posted by Seldaek:
Making a more comprehensive set of tests takes a bit longer than, say, making a handful of tests just for the sake of PR.lucideerTuesday, November 2, 2010 10:47:10 PM
Originally posted by Haavard:
Well I for one would welcome Opera producing a set of superficial tests that do well only in Opera purely for the sake of PR. 'Twould make a change...
mrdTuesday, November 2, 2010 11:58:34 PM
I'm glad - as long as it does not cause actual harm to the company and product - that Opera plays it straight down the line.
kailapisWednesday, November 3, 2010 12:13:51 AM
I believe the tests and their results are valid for the most part, although the relevancy of them and the conclusion many articles made are questionable.
d4rkn1ghtWednesday, November 3, 2010 2:35:01 AM
Artur „Jurgi” JurgawkaWednesday, November 3, 2010 10:10:22 AM
FransWednesday, November 3, 2010 10:14:19 AM
Originally posted by d4rkn1ght:
In a sense. But that was on Apple's marketing page, while this one is an upcoming official W3C test suite. The title, however, only said "Official HTML5 Test Suite Conformance Results." Luckily they've amended it now, and it has a big fat warning notice on there.
Originally posted by http://test.w3.org/html/tests/reporting/report.htm:
HaavardWednesday, November 3, 2010 11:47:22 AM
Originally posted by kailapis:
I addressed this in a previous comment:"Making a more comprehensive set of tests takes a bit longer than, say, making a handful of tests just for the sake of PR."
The problem is not that there are tests, but that people are jumping to conclusions based on that limited set of tests.
SeldaekWednesday, November 3, 2010 12:09:38 PM
Also, for once that IE gets better press than it deserves rather than people just bashing them no matter what kind of effort they put into their work to catch up, I think it's only fair to let them have this one.
kailapisWednesday, November 3, 2010 4:44:46 PM
Originally posted by haavard:
The tests that Microsoft provided were used for PR, but it's not just for PR. It's also to have a test so that people can argue about the specifics of implementing the standards. Microsoft invested a lot of man-hours creating the tests for W3C, and I don't really see any other browser vendor doing the same. Also, as Seldaek said, it has to start somewhere.
Originally posted by haavard:
Originally posted by kailapis:
Rafael LuikWednesday, November 3, 2010 6:58:13 PM
Originally posted by haavard:
Oops!HaavardWednesday, November 3, 2010 9:07:09 PM
Originally posted by Seldaek:
Originally posted by kailapis:
As mentioned, I already addressed this:"Making a more comprehensive set of tests takes a bit longer than, say, making a handful of tests just for the sake of PR."
In other words, other browser vendors are investing far more in more comprehensive tests, rather than rushing a handful of tests out the door. The problem is that the test suite was made available to the public far too early. It was a mistake on W3C's part.
YangombiUmpakatiWednesday, November 3, 2010 9:51:25 PM
Blaz(ž) PristavThursday, November 4, 2010 9:47:48 AM
Then some sites will work best only with IE9, how far did they get with this crap?
Cutting SpoonThursday, November 4, 2010 10:02:03 PM
At least on Test Drive, some examples have been fixed to support more browsers, and some actually broke in IE9 when they were repaired. The page on W3C includes a number of tests submitted (by Microsoft especially), and many of them have not been altered or audited since their submission. The test page is fundamentally broken at a low level.