4 ms·
The HTML5 test – How well does your browser support HTML5?
- yanw 17y agoChrome 5.0.342.9 beta: 137/160
- bostich 17y agoChrome 5.0.371.0 dev: 142/160
- samg 17y agoIt'd be more useful to have this list for all browsers, rather than just the one you happen to be using.
- bouncingsoul 17y agoTable of overall scores for different browsers: http://rakaz.nl/2010/03/the-html5-test.html http://rakaz.nl/2010/03/the-html5-test.html
- adzuci 17y agoI love the scores posted, I also love that I don't see any above me (Chrome 5.0.371.0) (yet), but I'd like to see a bit of a better breakdown. Anyone know of some info on some of the conflicts, like I'm missing a few in User Interaction, but I don't know who isn't. Or other html5 statistics sites, since the topic is a pretty common trend right now. Edit: (Like this: http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML_5) http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(H... in case its useful to anyone) I agree on the fact that there should be some differentiation between current html5 and proposed, (and that this site is hilarious: http://isgeolocationpartofhtml5.com/ http://isgeolocationpartofhtml5.com/), as well as some of the downfalls of scoring codec support that the author has mentioned, I think I like the out of 155 idea where chrome can go above it.
- PCheese 17y agoWebKit nightly r57408: 137/160
- labria 17y agor56990 — 143
- adzuci 17y agoHow does that work? It went backwards? And WebKit in what browser?
- pohl 17y agoNot sure, but if those are SVN revisions they could be on different branches?
- Zev 17y agoWebKit nightlies: http://nightly.webkit.org/ http://nightly.webkit.org/ And they probably enabled or disabled some features, based on what they're working on. For awhile (or, a few days, at least), Safari release was faster than WebKit nightlies on SunSpider, since they were working on strings in SFX (or something like that. Point I'm making is, release was faster and the slowdown was in the strings test).
- roschdal 17y agoInternet Explorer 8: 19/160
- JBiserkov 17y agoSame with the Platform Preview 9.00.7745.6019
- 0xdeadc0de 17y agoMozilla Firefox 3.6.3: 101/160
- deleted 17y ago[deleted]
- queensnake 17y agoLatest, ie Gecko/20100410 Minefield/3.7a5pre 20100410 (well almost latest): 102
- avar 17y agoNCSA Mosaic 2.7b6: None existant
- stuntmouse 17y agoSafari 4.0.5: 115/160
- j-g-faustus 17y agoOther OS X alternatives (on OS X 10.5): Opera 10.10: 38/160 Firefox 3.6.3: 101/160 Chrome 5.0.342: 137/160
- lukifer 17y agoWhere are WebSockets?
- adzuci 17y agoIsn't WebKit the only engine to support them now, and isn't in not formalized yet? But I think KAAZING would make support easily feasible without direct built in support so I'm not too concerned with including it in the score.
- deleted 17y ago[deleted]
- joubert 17y agoIPad Safari: 115
- deleted 17y ago[deleted]
- grandalf 17y agowow, chrome on linux scores 137. Higher than the latest firefox!
- omaranto 17y agoSafari on iPod Touch (3.1.3 OS): 113
- jackowayed 17y agoiPhone is the same, not surprisingly.
- deleted 17y ago[deleted]
- nkm 17y agoSame in Safari 4.0.5 on SL
- barrkel 17y agoAndroid (Nexus One): 118
- hackermom 17y agoSafari 4.0.5 / OS X 10.6.3/x86 - 120/160. I believe various configuration settings might affect the score.
- gloob 17y agoWhatever version of Iron that I'm using on Linux: 118.
- pufuwozu 17y agoI don't agree with the video ratings - codec support isn't defined in the HTML5 specification. It's not really fair to give a rating based on unspecified decisions. There's still a big debate about who's wrong and right, why should this test get involved? Surely some people will just see that Chrome gets 30/30 and think that Firefox/Safari are thus inferior.
- jgranby 17y agoOmniWeb 5.10.2 sneaky peek (v622.11 r128512): 113 (not in the rakaz.nl list)
- Sephr 17y agoCodec support isn't HTML5 support. Also, since when was MP3 audio/mpeg3 (which is tested)? The test should be for audio/mpeg. I know Chrome supports MP3.
- loup-vaillant 17y agoThat was an explicit choice: "In some cases the tests go beyond the specification." Given the current battle over codecs right now, I think this is a good choice.
- DrJokepu 17y agoThat doesn't change the fact that the correct MIME type of mp3 _IS_ audio/mpeg, not audio/mpeg3. It is a defect to test for audio/mpeg3.
- harlos 17y agoMidori 0.1.9 117/160
- BCM43 17y agow3m and links: Des not run.
- watty 17y agoThis proves HTML5 has a very long ways to go before replacing all 3rd party plugins.
- windsurfer 17y agoN900 default browser: 55 I'm pretty surprised at that. I expected higher due to it's Firefox roots.
- RyanMcGreal 17y agoFirefox 3.6.3: 101/160 Chrome 5.0.342.7 beta: 137/160
- kevinholesh 17y agoWebkit Nightly: 133/160
- sp332 17y agoFirefox nightly: 102
- natmaster 17y agoOpera 10.51: 102
- natmaster 17y agoH.264 codec support is NOT part of HTML5.
- Anon84 17y ago142/160 Chrome 5.0.371.0 dev on OSX
- jp_sc 17y agoThe tests for "section", "nav", "article", etc. fail in Firefox because it report them as "HTMLUnknownElement" not because they can't be really used and styled like any other element.
- duairc 17y agoI got 138 with Epiphany.
- natmaster 17y agoThis test seems kind of silly because it's testing things that aren't even close to becoming standards. Take Web SQL: http://dev.w3.org/html5/webdatabase/ http://dev.w3.org/html5/webdatabase/ The current version this test is based off, was put up this month by Google. Just a few months ago, SQL wasn't even in a draft document. Personally, I think it's destructive to put tests up on drafts that are so highly volatile. The biggest CSS bug in IE6 was because the initial definition of the box model was ambiguous about measuring width vs padding.
- paraschopra 17y agoI thought I will get a zero. But this site doesn't work in Lynx. http://www.yellowpipe.com/yis/tools/lynx/lynx_viewer.php http://www.yellowpipe.com/yis/tools/lynx/lynx_viewer.php