Fyrdility

by Alexis Deveria

When can I use…

Preview of the 'When can I use' page

A few weeks ago I was trying to find out which browser supported exactly which experimental feature, be it CSS3, HTML5, or something else. I found a couple of useful pages, but nothing quite as detailed as what I was looking for. Since I enjoy graphs, charts, and showing the world how much IE6 really sucks, I went ahead and made what I was looking for.

Thus was born the “When can I use…” page, which shows tables of a variety of current and upcoming web technologies. For all major browsers (Internet Explorer, Firefox, Safari, Opera and Chrome), versions for four different eras (past, present, near and far future).

The page can be customized to show only certain browsers/features/eras, so you have the option to ignore lesser used browsers or for that matter the most used one (it’s a lot of fun to pretend Internet Explorer doesn’t exist). I’ve also included a summary at the bottom of the page, which shows what percentage of the displayed features are supported.

Most features were tested myself, to ensure that the information is accurate. Please let me know if you notice any mistakes. Keep in mind that a “supported” feature may not actually work 100%, as well as the fact that some of the specifications are not set in stone yet, so what may be supported today may not actually work in the future. However, it is likely that in most cases the browser will update its support as the spec changes.

The feature list includes anything I personally feel is of significant use to web designers, but still lacks support in at least one browser version. I am open to adding more features, but only if it’s of significant importance and not just a detailed subset of another feature.

I intend to update the page as new browsers are released, or at the very least once a year. Due to its popularity, the page is updated as soon as new information becomes available.

Tags: , , , , , , , ,

187 Responses to “When can I use…”

  1. Jeff Schiller Says:

    As twittered, Safari didn’t have SVG support in 2.0, only 3.0.

  2. Alexis Deveria Says:

    You’re right, thanks Jeff! Fixed now.

    I think the ASV plug-in fooled me when I tested that…

  3. Rijk Says:

    You should move Opera 10.0 to the ‘Near future’ row in your tables, it will surely not be delayed all the way into 2010 – but then remove the Video features from the lab builds to a later 10+ version for ‘Future’.

    You seem to be really strict about saying ‘not ready’ for everything because you apparently need IE6 compatability… makes the list rather fatalist :)

  4. Alexis Deveria Says:

    @Rijk – Thanks for the info! I’ll make the necessary changes. Surprised to hear the Video features aren’t expected to make it in O10, since they seem to work pretty well and Firefox will be releasing them in FF 3.1 (and webkit has support now, albeit without native ogg theora support).

    And yes, IE6 is the obvious sore thumb here, but that’s why there’s the checkboxes at the top. You can turn off the “Past” time period, turn off Internet Explorer alltogether or enable the alternatives, and the conclusion info will change automatically.

    I’d also be happy to add significant features supported by IE, but lacking support elsewhere (not including MS proprietary stuff of course). I just haven’t really found any. Contenteditable is a possibility, but is it really that important to designers?

  5. Alex Russell Says:

    Fantastic work.

    One note: iPhone has CSS 3D transforms but it has not landed in either webkit proper or Safari or Chrome.

  6. Vsync Says:

    This is so awesome.. but makes me sad about the poor poor condition the web is at present times. not to mention me want to go and kill every IE user, just so i won’t have to bother with that browser ever again.

  7. Alexis Deveria Says:

    @Alex

    Thanks! And you’re right, has now been fixed. Must’ve just lumped that one together with those other webkit features.

    @Vsync

    If it makes you feel better, the tables largely consist of features for standards still in development, IE8 does okay with many features not mentioned in the list. Of course the lack of support for older web technologies like XHTML, SVG, etc. is inexcusable, and I certainly know how you feel.

  8. Oliver Says:

    The past for Safari is Safari3.1 or Safari 3.0 — Everything Safari3.2 supports was supported in 3.1.

  9. Konstantin Says:

    Currently using FF 3.2a1pre, the WYSIWYG editable elements example is *not* working.

  10. Myra Says:

    Chrome 2 is already out. I tested @font-face, text-shadow and CSS animation, they work. Video doesn’t. Anyway, in most features Chrome is on a par with Safari because it’s the engine that matters.
    @Konstantin: Strange that contenteditable should not work in Fx3.2a, it works fine in Fx3.1b2. I couldn’t find anything in bugzilla.mozilla.org about a contenteditable regression. You should file a bug.

  11. Eric Says:

    Looks like we are always going to be waiting for that awful IE browser. IE8 and IE9 21% stupid IE

  12. Jeff Schiller Says:

    Alexis,

    Is there a way to get a permalink to a particular table? I notice you ID each table (div id=”css-media”), but I couldn’t figure out a good way to use that based on your URL frag/query structure.

    Jeff

  13. Chris Says:

    This site is so awesome! However I don’t think that Firefox does HTML5 client-side database storage in any versions yet.

  14. Alexis Deveria Says:

    @Oliver – Yeah, I think I may replace Safari 2 for that. Thanks for the reminder.

    @Konstantin – It may not be the best example in the world, and being in a pre-alpha state, FF3.2 can be expected to have bugs like that.

    @Jeff – Not currently, but good point. I do intend on adding a method that allows that. For now I would suggest using the category links, though you probably already figured that one out.

    @Chris – Thanks! You may be right, I believe I have mistaken the localStorage and sessionStorage support in FF for that. I’ll do some investigating and fix that table.

  15. radex Says:

    Opera 9.5+ supports text-shadow.

  16. Alexis Deveria Says:

    @radex – It sure does. Fixed now.

  17. Alison Says:

    Great article! It was nice to know where everything stands. :)

  18. Lewis Francis Says:

    Hey, great resource — fwiw, I’m pretty sure transparent png support was available in Safari from the very beginning.

  19. Mike Kompar Says:

    Excellent info!!!!! One concise view of everything. Mind if I cross post this to my Web Standards LinkedIn group?

  20. Alexis Deveria Says:

    @Alison – Thank you!

    @Lewis – Thanks! And yes it was, is there anything on the page to indicate otherwise? As shown in the alpha PNG table, IE6 is the only one that doesn’t support it.

    @Mike – By all means, go right ahead!

  21. Dan Says:

    This is very interesting, especially if it’ll stay somewhat up-to-date.

    To show my appreciation, here’s a link which i think would fit nicely among your CSS-support resources links: http://www.webdevout.net/browser-support-css

  22. radex Says:

    Web Forms 2.0 JS solution for IE:

    http://dean.edwards.name/weblog/2005/05/wf2-ie/

  23. Jaakko Says:

    PNG alpha transparency for present IE (7.0) is marked as supported. This is not true. Try to change the opacity (using filter: alpha) for element containing transparent PNG (32-bit) and see what happens: transparent pixels becames black. IMO IE7 only *partially* supports PNG alpha transparency.

  24. David Says:

    Is it intentional that the alternatives (at least js) don’t have an influence on the Summary results ?
    If so, why ?

  25. Alexis Deveria Says:

    Sorry for the late responses everybody…

    @Dan – Thanks, I guess I could add links to some of the tables on that page, assuming that’s what you mean.

    @radex – Thanks!

    @Jaakko – I certainly see what you mean, but don’t think changing the opacity of a PNG happens enough to say there’s only partial support. I would say that’s more of an issue with the MS filter property.

    @David – Good question. I believe it was intentional when I decided to do that, since I felt the summary should really only take into account the browser’s actual capabilities.

  26. James Says:

    Another update: Firefox 3.2 nightlies have support for multiple backgrounds.

  27. Alexis Deveria Says:

    @James

    Neat, thanks!

  28. David Says:

    Alexis,

    How about VML, HTML+TIME, XHTML+SMIL, XHTML+Voice, Widgets ? (sorry, heard you tweet about other potential technologies to include)

    Can you provide info about each alternatives ?

    thanks

  29. Alexis Deveria Says:

    @David – Thanks for the suggestions! I think I need to make a FAQ or something. :)

    For now I’d like to only include items that meet the following criteria:

    1. Useful to web designers for web sites
    2. Likely to be eventually implemented by the majority of browsers
    3. Currently implemented by at least one browser
    • VML: Was replaced by the W3C with SVG, really don’t see it passing #2
    • HTML+TIME: Was replaced by the W3C with XHTML+SMIL, so no #2
    • XHTML+SMIL: No implementation at all yet, from what I can tell. So no #3. Admittedly not sure of #1 or #2 either.
    • XHTML+Voice: Hm…yeah, okay. Good one!
    • Widgets: Not really a web design feature, so I’m not sure about #1. But maybe.

    Note that I’m open to re-evaluating those criteria. I don’t want to anti-Microsoft, but also I don’t want “never” to be the answer to question to “When can I use”. And if it becomes evident that no other browser is interested in adopting Webkit’s proposals, I’ll remove them too.

  30. David Says:

    I’m sorry. I was just throwing specs out of my head. Ok with the criteria.

    I’m not sure for XHTML+TIME : it doesn’t quite replace HTML+TIME, as XHTML doesn’t replace HTML. So it’s the only way to animate HTML declaratively for the moment.

    About XHTML+SMIL, do JS alternatives count for #3 ? If so, FakeSmile does currently work in Opera, Safari and Firefox. I mean to the question “can i use XHTML+SMIL?” the answer is “yes if you include a JS hack”.
    For #1, ask Jeff Schiller what he thinks.
    For #2, well… mentioning the spec on your page will give it more visibility :-)

    thanks !

  31. Ivan Says:

    PNG Support: Internet Explorer up to and including version 7 don’t include gamma information in PNG files. Solution: remove gamma chunk from PNG files (this way you loose great PNG feature).

  32. radex Says:

    Ivan, you’re wrong. Gamma information in PNG for me (webdeveloper) is very problematic, because I use pngs in backgrounds, gradients etc.

  33. radex Says:

    … oops, sory.

    … and there’s no gamma information in CSS. In Opera or Firefox it isn’t problem, but in Safari on mac I see ugly transition gradient -> solid color. And I must use tool like pngcrush (on OSX I recommend these tools: http://pornel.net/imageoptim/en http://pornel.net/imagealpha – it helps)

    Sorry for my english ;)

  34. David Says:

    Opera 9.5+ seems to support the Audio element : http://www.opera.com/docs/specs/opera95/#html

  35. David Says:

    Thanks for the change Alexis. Btw, presto 2.1.1 (opera 10) seems to support element (per http://www.opera.com/docs/specs/presto211/#html ) in addition to the object.

    cheers

  36. Alexis Deveria Says:

    @David

    Thanks for info! And FYI, I’m still looking into the XHTML+Voice support as well as XHTML+SMIL. Out of curiosity, are you interested in seeing XHTML+SMIL support for any particular reason?

  37. David Says:

    Thanks a lot @Alexis.
    I just heard you calling for ideas of new technologies you might want to add. First, as the fakesmile author, it’s the very first thing that came to my mind. Second, in my experience, I guess it would be pretty straightforward for implementors to extend svg+smil to the xhtml ns. (Timesheets is a bit trickier though)
    (I like css transitions, but not the complicated and incomplete css animations, yuk. but hey i might be biased)
    So, I think what xhtml+smil misses the most is advertising :-)
    Though, I have mixed feelings about mentioning fakesmile as it could serve as an excuse for not implementing it natively… :-/

  38. Alexis Deveria Says:

    Ah, see, would have been helpful to know you’re the Fakesmile author. :)

    I’ve added XHTML+SMIL, but since the status is “W3C Note”, which apparently doesn’t mean much, I’ve put it under “Unofficial / Note”. I may also do the same for XHTML+Voice, which is also only a “Note”. That or change it to just “VoiceXML”, but I think that might be straying too far from regular web design.

  39. Josh Says:

    Webkit (Safari and Chrome) only has partial support for multiple backgrounds. Try three background images with three different positions.

  40. Alexis Deveria Says:

    @Josh

    Seems to be working fine for me in the tests I tried…could you be more specific about what the CSS looks like when it doesn’t work?

  41. Josh Says:

    I have since rewritten the code where I ran into this so I don’t really have a test case for you, but here’s all the relevant details I can think of:

    It might just be textareas. I had a form script that was creating and appending textareas with DOM methods. If the CSS rule applied to them had three or more background images defined, all of the background images would render (and in the correct stacking order and everything) but lose their positioning. I don’t know if it matters, but it was a single .PNG sprite being used for all of the background images. Also, a “resize: both;” declaration was in the rule.

    On another note, I think “inline-block” might be missing form this list.

  42. Dan Says:

    Regarding SVG support, i know of 2 javascript workarounds to get it working in IE (by feeding it VML instead): dojox.gfx and Raphael. AFAIK they’re both limited on the common denominator in functionality, though.

    I don’t know if that qualifies as a workaround for you. Just to let you know.

  43. Dan Says:

    Same goes for WebForms2: http://code.google.com/p/webforms2/

  44. Lars Gunther Says:

    a. Very useful table with lots of information. Thank you!

    b. Suggested improvements.

    Lumping together Safari 3.1 as both past and “far past” is misleading. Safari 3.1 was launched only slightly ahead of Firefox 3. Are you really sure that Safari 3.0 is dead?

    The heading “When can I use…” is also misleading with the conclusions, since they do not factor in progressive enhancement. I can use e.g. rounded corners today. I just have to accept the fact that MSIE and Opera users don’t see them, but nothing breaks.

    Have you considered adding JavaScript 1.6+/EcmaScript version 5 (aka 3.1) features as well?

  45. Alexis Deveria Says:

    @Dan

    Thanks! Those certainly seem worth adding.

    @Lars

    Firstly, thanks!

    Secondly, thanks for the feedback.

    Actually, “Far past” was only added when IE8 was released, and I didn’t want to remove IE6 (since we generally still need to support it). It’s not really accurately named, I have to admit. And looking at the latest Hitslink stats, Safari 3.0 is used less than Netscape 6, so it just doesn’t compare to the IE6 share. Same for Firefox 1.5.

    The idea is that if you don’t care about how something works in a certain browser, you can simply uncheck it and the conclusion will change appropriately. I guess “When can I use” technically means “When can I use a given feature in a fully supported interoperable way”, but that gets a bit long. :) The point you make about progressive enhancement is a good one, however. Maybe I can find a way to specify features that “don’t break” things.

    And yes, I’d thought about adding JS/ES features to the list, seems only appropriate. Just haven’t taken the time to investigate them or do any browser testing on them. If you happen to any good resources that would help with this, that would be great. Thanks again!

  46. Something Witty Goes Here Says:

    [...] a big fan of Alexis’ When-Can-I-Use site. I liked it so much that I asked him to let me link directly to when a specific feature will be usable. He obliged. Here is an example [...]

  47. Weston Says:

    Thanks!

  48. Elijah Grey Says:

    Under XDM, you have Opera 9.6 as fully supporting it, though it does not. Opera 9.6 does not support MessageEvent.origin and instead has MessageEvent.domain, which isn’t a valid HTML5 origin.

    It can be partially fixed (though it just assumes the protocol is http:) with this:
    if (typeof window.opera != "undefined") { // Opera 9.x MessageEvent.origin fix (only for http:, not https:)
    if (parseInt(window.opera.version()) == 9)
    Event.prototype.__defineGetter__("origin", function(){
    return "http://" + this.domain;
    });
    }

    PS. You should add support for <codeblock> or >pre< tags in comments. I have no way to express my code in an easy-to-read manner otherwise.

  49. Elijah Grey Says:

    Error in last comment, I meant <blockcode> instead of <codeblock>

  50. Henri Sivonen Says:

    It seems that the note about Opera on the @font-face feature is wrong. Opera doesn’t support .otf fonts, but .ttf is downloaded even if format(“truetype”) is specified.

  51. Alexis Deveria Says:

    @Elijah

    Hmm…I see what you’re saying, but the basic functionality still largely works, right? As mentioned in the FAQ, there may not be 100% support. If you still feel this lack of support is particularly significant for its usage, let me know. I’ll also be happy to add a resource link about that feature if you can suggest a page that describes any browser shortcomings for XDM.

    Also, I’ll see what I can do to allow better code display in comments, thanks!

    @Henri

    I’ve changed the wording, since you’re right about the format(“truetype”) part. Thanks! However, Opera does appear to support OTF fonts without that declaration. This is mentioned in the changelog and can be tested by removing ‘format(“opentype”)’ on this demo page.

  52. Elijah Grey Says:

    @Alexis Deveria
    MessageEvent.origin is the ONLY way to ensure that you can trust a message. Without it, the feature should be classified as broken. There is no way in Opera 9.6 to know what origin a message truly came from without making a wild guess using MessageEvent.domain.

  53. Nico Hagenburger Says:

    Awesome collection, thanks! I’ve got one comment for “New, stylable HTML5 elements”: It works well with Firefox 2.0 if you serve the document as application/xhtml+xml. See my my blog post about HTML5.

  54. Josh L Says:

    How about adding print CSS limitations to this excellent resource?

    Like the page-break-inside property, for example.

  55. Fabien Ménager Says:

    Thank you for this wonderful tool ! :)
    Is there a way to have more details about the JS solutions ?
    I suggest a few more JS solutions for the Canvas Text support : ExCanvas has now the text drawing API : http://explorercanvas.blogspot.com/ and I suggest you a lib that completes the canvas text API for the browsers that don’t have it : http://code.google.com/p/canvas-text/
    I don’t know if this solution is acceptable, but I just wanted to let you informed.

  56. Alexis Deveria Says:

    Thanks, glad you like it!

    And certainly, those are good links, I’ll be happy to add them.

  57. Magne Andersson Says:

    Nice work, perfect for web developers, and I’ll certainly look at it in the future :)

    Have you considered adding Geolocation support, which I think only Firefox 3.5+ supports currently?

  58. Magne Andersson Says:

    Apparently, Chrome 2 supports it too.

  59. Alexis Deveria Says:

    Thanks for the tip! The feature has now been added.

  60. Magne Andersson Says:

    I’m sorry, apparently Chrome 2 does not support it, and I should’ve checked my sources better (including testing it myself). According to this, http://html5demos.com, it is supported by Firefox 3.5 and iPhone (MobileSafari then?) only.

  61. Magne Andersson Says:

    But then again, I see you marked it as 2.x. Does that mean you tested it yourself, and it worked on 2.1+, as I’m running 2.0.

  62. Fabien Ménager Says:

    I think the note

    “Far past” exists only for IE6, as it is often the only really old browser people need to support.

    can be removed now :)

  63. Magne Andersson Says:

    I’d love to think so to Fabien, but I think there’s still a lot of people out there who thinks IE6 support is important.

  64. Fabien Ménager Says:

    Of course, and that’s very sad, but I said that because Firefox 2.0 and Safari 3.1 are in “Far past” too, now.

  65. Alexis Deveria Says:

    @Fabien – Indeed, I have removed the note. Thanks!

  66. Darxus Says:

    The category link for Summary doesn’t work. All the values are NaN%. I see you started adding permalinks, but they’re broken. Whenever I use the links from a different page, or open in new tab, instead of the table I want, I get “Um…dude.”

    This page is awesome.

  67. Darxus Says:

    Actually, I really think you should put the Summary table at the top. That one is particularly awesome.

  68. Norman Says:

    your table needs a small update: Firefox 3.5 does support (I dont know how much of it tho) Web Storage Features
    see this link

  69. Norman Says:

    oh and it also supports 3d transformation (example) :)

  70. Alexis Deveria Says:

    @Darxus – Thanks! Since the summary table varies based on the other tables displayed, it doesn’t actually work by itself. And as much as I like it myself, I don’t want it to be too prominent since the numbers are essentially quite arbitrary. While they provide a general idea of how well browsers are supporting upcoming/new features, I’d hate to see people making specific claims based on those numbers.

    Also, the permalinks work for me (aside from the Summary one)…What browser are you using?

  71. Alexis Deveria Says:

    @Norman – Indeed it does, which is why it appears as supported on this table. However, it does not support any of the database features currently supported in Webkit.

    Also the “3D” effects on the page you link to are actually done with just 2D transforms, as the article itself explains. :)

  72. Magne Andersson Says:

    Sweet, we’re getting CSS transitions in Firefox too soon :)

    https://bugzilla.mozilla.org/show_bug.cgi?id=435441 – Milestone is the Mozilla 2.0 engine (used in Firefox 4.0), but as the patch is already submitted, that might mean that it shows up as early as for Gecko 1.9.2 which is used in Firefox 3.6.

    But, I think you can safely mark it as 4.0 and 4.* for Firefox.

  73. Rob Says:

    The selection on this page is very biased. For instance:

    * For CSS 3 it show working drafts even but not candidate recommendations like Ruby and TV profiles.
    * Canvas is shown as a separate standard even though it is only a part of an HTML5 working draft

    For CSS3 the page should use this list.
    http://www.w3.org/Style/CSS/current-work
    Not make it a biased list of its own !!!

  74. Alexis Deveria Says:

    @Magne – Cool, thanks for pointer! Feature support has been noted (and I went ahead and changed 4.0 to 3.6)

    @rob – That is correct, it is biased towards the features I have personally noticed web designers/developers show a specific interest in. Canvas is a category of features, and appears on its own due to the amount of interest shown in the technology around the web.

    Since I have yet to hear anyone talk about wanting more Ruby support or implementation of the TV profiles (does any browser even support this?), I have not added them.

  75. iveinsomnia Says:

    I’ve maybe wrong but the SVG fonts test work fine for me:
    SVG 3.0 under IE8

    (XP32 Pro SP3 – IE 8.0.6001.18702)

  76. Alexis Deveria Says:

    Yeah, I’m pretty sure you’re mistaken…you may have the Adobe SVG viewer plug-in installed, which would might be rendering it for you in IE8.

  77. Brian Campbell Says:

    Chrome 3 was just released, and it supports both <audio> and <video>. For some reason, you have it listed as not supporting <audio>. You might want to update that!

    Thanks for the great resource. It’s pretty helpful to be able to get a high-level overview of the progress on all of this stuff.

  78. Jim Says:

    There is a an alternate JS solution for border-radius, called CurvyCorners, which works in IE and, they say, in Opera.

  79. Lars Gunther Says:

    Have you thought about adding SVG clip paths and paint servers to your table?

  80. Magne Andersson Says:

    Turns out that CSS transitions won’t make it into Firefox 3.6, but instead in 3.7.

    Also, 3.6 is quite locked from getting new features now, I think you can safely mark everything that is currently grey as red. Seeing that HTML5 form features is also grey, it seems that support for the “multiple” attribute will come with 3.6. Maybe not enough to justify the partial status?

    And last, I thought the list page itself had stopped being updated, as I was often looking at the RSS feed and saw no new updates. It would be nice if you kept that up to date.

    Thanks!

  81. Alexis Deveria Says:

    @Lars – I’ll look into it, but I’m not sure if the average web developer would be interested in overly specific SVG feature support.

    @Magne – Thanks for the info, will update soon. And I apologize for not having updated the feed recently, forgot all about that after the latest changes. Glad to hear it’s being read though, I’ll update it too shortly with the changes I’d forgotten to mention. 

    Also congrats for having posted the 666th comment on this blog. :)

  82. Lars Gunther Says:

    @alexis:

    Re: clip-paths and paint servers. The usage of SVG filters on HTML content will be of interest. It is not about SVG features per se, but the SVG features interacting with HTML content.

    Have a look at http://people.mozilla.com/~prouget/demos/round/index.xhtml in Firefox 3.5+

  83. Magne Andersson Says:

    Small note:

    http://dev.w3.org/csswg/css3-images/ – I think CSS gradients have now been accepted by the W3C, but the accepted solution is the one proposed by Mozilla instead of the one by Webkit (which is the one you have listed). Therefore, Firefox 3.6+ supports the correct way to do gradients, while Safari/Google Chrome (?) has the “Partial/Incorrect” status, but support for the Mozilla solution is being worked on.

  84. Remy Sharp Says:

    Hi Alexis, I thought I’d let you know (if you hadn’t noticed already), I bought http://whencaniuse.com and pointed to your app. I love the functionality, but always forget the url, so I figured this would fix it :)

  85. Rick Walter Says:

    Hi Alexis

    You show Firefox as fully supporting MathML, which is incorrect. MathML has two parts, Presentation Markup and Content Markup. Firefox only supports the Presentation Markup part of the specification.
    It does fully support the Presentation Markup tho.

  86. David Says:

    Hey Alexis,

    I just notice WCIU doesn’t mention Template Layout ! :-o

    Don’t you know that css module ? ;-)

    David

  87. Dan Says:

    Merry Christmas!

    Opera 10.5 alpha has been released a few days ago. Here’s what’s new: http://my.opera.com/ODIN/blog/opera-10-5-pre-alpha-build-released-here-is-whats-new

  88. Szczepan Says:

    Blah, blah, blah… Everything is “not ready”. Standards sucks. It is stll not ready even if it is html 3.2, 4, 4.01 or Special IE XHTML 12 Nitro Edition. I hate websites of web designers. Everyone can make site (using greart features in top most applications – all over the world – like MS Office), even if it will works great only in top most world wide web browser: Internet Explorer. People do not care for tech-specs for webpages, just like do not take care to understand differences between “browser”, “search engine” and “Internet” – it is for about 75% of people: just “the same”(!!!).

  89. Magne Andersson Says:

    @Szczepan You sound like a frustrated Internet Explorer user who is shocked by how bad your browser performs ;)

    Standards matter. Without standards the web wouldn’t work. How would the different browsers know how to render things?

    People do care about who codes sites, no matter if they understand the mechanics behind or not. Generators like MS Office (eew) generates tons of unnecessary code that makes site load slow. People want sites to load fast, and look good. You can’t do that with MS Office.

    And for one last note, IE is going down. Use it and you are aboard a sinking ship.

  90. Stac Says:

    Just to mention…

    IE has support for VIDEO & AUDIO elements at least 10 years (since IE 5) as part of XHTML+SMIL (former HTML+TIME) module.

    Unfortunaly too few developers knows about that.

    Opera and Mozilla sucks in this case. If they would have implemented VIDEO support as decribed here (http://www.w3.org/TR/NOTE-HTMLplusTIME), we would already have widespread VIDEO use.

  91. Magne Andersson Says:

    Your argument doesn’t really hold up. If IE implemented this 10 years ago, when it was basically alone on the market (with 95%+ marketshare), why didn’t web designers start using it?

    Sounds to me like something was wrong with IE’s implementation.

  92. Alexis Deveria Says:

    Sorry for the belated responses, but here goes:

    @Lars – I think I already have that covered with “SVG effects for HTML”?

    @Remy Sharp – Awesome man, that’s very very cool. As tweeted before, I feel flattered. :)

    @Rick Walter – Interesting, I’ll need to investigate that further. Happen to have a link for me with more info?

    @David – :D If you look at the FAQ, you’ll see that a feature needs to have at least one implementation to make it to the list. So unfortunately I can’t add that one.

    @Dan – Thanks for the link, I managed to update WCIU on the day that news arrived. :)

    @Szczepan – What Magne said. Also note that When Can I Use… is not for people to pick out the best browser, it’s for designers/developers to know when tools are available to them to make web development easier, make web pages load faster, and make websites work better (and do more than was possible before).

    @Stac – You raise an interesting point. However, since neither HTML+TIME nor XHTML+SMIL made it past the “Note” stage in the W3C, it’s not reasonable to have expected other browser makers to implement the feature. Since clearly there is an interest in video and audio elements by browser makers, there must have been a good reason for the W3C not to standardize this particular specification.

  93. Rick Walter Says:

    Links for MathML in Firefox

    The mathml project page on mozilla.org. None of this is anywhere near recent.
    This says that Mozilla is only doing the mathml 1.0 presentation and maybe some of mathml 2.0

    The W3C Mathml Test suite on w3c.org seem to work correctly! But they don’t really. There is an xsl file (c2p.xsl is included in mathml.xsl) that transforms the mathml-content into mathml-presentation! View frame source and then try saving the frame source as ‘web page complete’. You get an xml file with the mathml-content replaced by the equivalent mathml-presentation.

    If you copy the example code from the test pages into your own file (either xhtml or mml) they don’t work. I’ve posted the ‘cn2′ test on my site.

  94. Rick Walter Says:

    More on MathML

    It seems that even the W3C requires an XSL transform/stylesheet to display mathml-content. The W3C’s Putting Mathematics on the Web has a link to test if a browser supports mathml-content. That test page has an xsl stylesheet that transforms content form to presentation form. They even recommend that you use and/or link to their xsl style sheet!!!

    So I guess that it’s enough that a browser supports all of MathML presentation and xsl stylesheets. With this criteria, Firefox does support all of MathML.

  95. David Says:

    @Stac – XHTML+SMIL is there under Status Unofficial / Note.

    @Alexis – XHTML+SMIL also has only a JS implementation, and you considered it was enough to make it to the list. Template Layout should have the same status, imho.

    Btw,
    - what about XHTML+Voice ? (see your comment #38)
    - What about Cross-Origin Resource Sharing ? http://www.w3.org/TR/access-control/

    cheers!

  96. Alexis Deveria Says:

    @Rick Walter – Thanks for doing that research! Good to hear Firefox’s support is still sufficient.

    @David – The only reason XHTML+SMIL gets to be in is because IE has some form of support for it. :)

    There doesn’t seem to be much interest in XHTML+Voice by other browser makers or by web designers/developers, so it doesn’t seem appropriate to add to WCIU.

    Cross-Origin Resource Sharing, on the other hand, does seem appropriate to add, so I’ll do more research into that. Thanks for the reminder!

  97. Frank G Says:

    How come you are not including Web Sockets and Web Workers?

  98. Gaurav Says:

    Nice work.

    There are a lot of DOM 2 / DOM 3 basic stuff that IE still doesn’t support in version 8. Most noticeably the W3C event model. You may want to consider adding that. You can find a lot more examples on the first two buckets of the Acid 3 Test. A lot of frameworks like jQuery are providing workarounds.

  99. Fabien Ménager Says:

    Hello, It looks like the Canvas Text API is now supported by Opera 10.5 beta.

  100. Drazick Says:

    I think Chrome 5.0 supports the File API

  101. madsenfr Says:

    Nice job !
    But I notice some wrong support value :

    - Audio et Video are not supported by Safari (at least on Windows version).
    - Drag ‘n Drop is supported by all except Opera.
    - Offline application is not supported by Chrome.

    I made demonstration and support tests on http://w3c.html5.free.fr

  102. RJ Says:

    Would you be able to add a category for ruby support? Not the programming language but the writing system used a lot in asian languages. http://en.wikipedia.org/wiki/Ruby_character

  103. Peter Lubbers Says:

    Hi Alexis,
    Thanks for this most excellent resource!
    I point this page out to all the people that attend my HTML5 training course. Great stuff.
    2 questions:
    1) The Web GL support does not look right for Chrome 4.0. AFAIK it is only in nightly builds. Same for Opera (I don’t think it ships in 10.5) Can you verify that?
    2) I was surprised not to find WebSocket covered. Current coverage is Chrome 4+, Nightly builds of WebKit, Planned in FF3.7 and Opera (version TBD).
    Regards,

  104. Alexis Deveria Says:

    @Peter

    1) Yes, you’re right. I’ve updated accordingly. Thanks!

    2) WebSockets was included, but at the time I added it it was only an “Editor’s Draft”, which would put it as “unofficial” (hidden by default). Have changed it now to “Working Draft”. Thanks!

  105. Mike Says:

    Box-sizing does not work “as is” yet in FFox 3.6, Safari, Chrome. You still need to use “-moz” or “-webkit.” It does work as is in IE8 though.

  106. Magne Andersson Says:

    @Mike Then IE8 is doing it wrong. Until the module reach the Candidate Recommendation status, the prefix must be kept.

    On another note, I think you could remove the supposed support for SVG Fonts in Firefox 3.7, as there isn’t a patch, nor even a discussion about it right now. But, also, I think you should add the “partial/experimental” status for Firefox 3.7 when it comes to “HTML5 form features” as support for many of these are due to be checked in very soon (see https://wiki.mozilla.org/User:Mounir.lamouri/HTML5_Forms).

  107. Brian Says:

    You’ve marked Web Workers as supported in a few browsers, yet FF and Safari have only implemented Worker, not SharedWorker. Perhaps set up a separate section for SharedWorker?

  108. Magne Andersson Says:

    Looking at “HTML5 form features”, I see that Opera, for example, has the full support ranking despite not supporting all of the types. This is not a compliant of that, instead, I think it’s correct if they almost support everything. That is, why I am asking you to also set a full green status on Firefox 3.7′s SVG Animation (SMIL) as two patches are soon to land which will give support for 4 out of the total 5 SMIL parts. The last unsupported part is called “animateColor” which is basically just duplicating current functionality with a few restrictions. I think the support is enough to have a full green status. Thanks!

  109. Alexis Deveria Says:

    @Brian – Hm, will look into it. Thanks!

    @Magne – Looking at http://www.miketaylr.com/code/input-type-attr.html I would have to say that Opera supports “almost everything” where others seem to have partial support. I do agree it’s hard to decide where to set the threshold.

    However, the SMIL support in FF sounds good, so I’ve set that to “Supported”. Will review again once 3.7 is released and codedread updates his SVG support chart. Thanks!

  110. Austin Says:

    Can you add WebGL to the list?

  111. Alexis Deveria Says:

    @Austin – Already was added, just hidden by default by having been set to “unofficial”. Changed now though, as they’ve published their spec.

  112. Magne Andersson Says:

    The Gecko HTML5 parser is now enabled by default, which means that “Inline SVG in HTML5″ is a full green for Firefox. Now there’s just some HTML5 form features left before Firefox has 100% HTML5 support in the “When can I use…” charts :-)

  113. Dustin Hansen Says:

    Hey Alexis,
    Just wanted to say thanks for all the hard work! You’ve really made keeping up on specs much, much easier! :-D

  114. Lars Gunther Says:

    Suggested updates (Hope this works without the PRE-tag):

    // Addition
    'mathmlinhtml':{
    'title': 'Inline MathML in HTML5',
    'description': 'Method of using MathML tags directly in HTML documents',
    'spec': 'http://dev.w3.org/html5/spec/the-canvas-element.html#mathml',
    'status': 'wd',
    'links': [
    {title:'Mozilla Hacks blog post',url:'http://hacks.mozilla.org/2010/05/firefox-4-the-html5-parser-inline-svg-speed-and-more/comment-page-1/', date:'2009-05-11'},
    {title:'Demo page', url:'http://hsivonen.iki.fi/test/moz/html5-hacks-demo.html', date:'2010-05-11'}
    ],
    'categories': ['Other', 'HTML5'],
    'stats':{
    'trident': {6:'n',7:'n',8:'n',9:'y'},
    'gecko': {2:'n',3:'n',3.5:'n',3.6:'p',4:'y'},
    'webkit_saf':{3.1:'n',3.2:'n',4:'n','4x':'u'},
    'webkit_chr':{.2:'n',1:'n','1x':'n',2:'n',3:'n',4:'n',5:'u'},
    'presto': {9:'n',9.6:'n',10.1:'n',10.5:'n','10x':'u'}
    },
    'notes': 'Currently only works in Firefox 3.6 by enabling the HTML5 parser in about:config (not recommended)'
    },

    // A few more notes
    'svg-html5':{
    'title': 'Inline SVG in HTML5',
    'description': 'Method of using SVG tags directly in HTML documents',
    'spec': 'http://dev.w3.org/html5/spec/the-canvas-element.html#svg-0',
    'status': 'wd',
    'links': [
    {title:'Mozilla Hacks blog post',url:'http://hacks.mozilla.org/2010/05/firefox-4-the-html5-parser-inline-svg-speed-and-more/comment-page-1/', date:'2009-05-11'},
    // Added link
    {title:'Demo of multi-browser support using the SVGWeb library',url:'http://codinginparadise.org/projects/svgweb/samples/javascript-samples/svg_inline.html?svg.render.forceflash=false'},
    {title:'Test suite', url:'http://samples.msdn.microsoft.com/ietestcenter/html5/svghtml_harness.htm?url=SVG_HTML_Elements_001', date:'2010-05-07'}
    ],
    'categories': ['SVG', 'HTML5'],
    'stats':{
    'trident': {6:'p',7:'p',8:'p',9:'y'},
    'gecko': {2:'p',3:'p',3.5:'p',3.6:'a',4:'y'},
    'webkit_saf':{3.1:'p',3.2:'p',4:'p','4x':'u'},
    'webkit_chr':{.2:'p',1:'p','1x':'p',2:'p',3:'p',4:'p',5:'u'},
    'presto': {9:'p',9.6:'p',10.1:'p',10.5:'p','10x':'u'}
    },
    'notes': 'Currently only works in Firefox 3.6 by enabling the HTML5 parser in about:config (not recommended)'
    },

    Would you like me to contribute data for WOFF (it deserves even more exposure than SVG-fonts), offline/online detection, calc(), ECMAScript 5 and 6 features (ECMAScript is not in this chart at all right now…),

  115. Lars Gunther Says:

    Thank you for providing this resource. I think it is the most usable one on the net right now. But nothing is perfect and I have a few suggestions for how it can be improved:

    ARIA support in Chrome and safari is not complete but spotty.

    There is no distinction between experimental support and the real deal. In some cases the difference will be quite drastic (think CSS gradients where Webkit’s original syntax has been completely changed by the CSS WG). How about adding “experimental” as yellow?

    HTML5 forms is not completely implemented by any browser. Opera comes very close, but still no cigar. Webkit and Mozilla are making rapid progress right now, though. Opera should be listed as partial and the closeness perhaps explained in a note. Another path would be to split up HTML5 forms into several categories: DOM API, Widgets, contraints (= will not submit invalid data).

    BTW, I forgot the spambot detection question and when I used the back-button all my text was gone. That was not cool! Way too draconian.

  116. Alexis Deveria Says:

    Thanks Lars! I’ve updated the Inline SVG in HTML5 feature with your link and note. Currently I’m still trying to decide what to do with MathML in HTML. Unlike SVG, which can be useful to probably all web developers, MathML support is only useful to a very small subset. Therefore I’m not sure if it’s worth adding as its own entry.

    As for the rest of your suggestions:
    - WOFF: What additional contribution do you have in mind?
    - offline/online detection: Falls under “Offline web applications”
    - calc(): Is this supported by a browser of any kind yet? If so, yes, would be great to have.
    - ECMAScript: Yeah, I’ve been trying to decide whether or not to add this…probably should.

    - ARIA: Great link, thanks! Will update accordingly.
    - Experimental/real support: As long as the developer can accomplish the same effect, I don’t think the difference really matters, assuming the implementations are close enough. For gradients you may be right, I should probably change that. I wouldn’t call Firefox’s implementation there the real deal though, it’s still experimental and the spec can change.
    - HTML5 forms: If you read the FAQ, you’ll see that “supported” doesn’t mean 100% supported, just a great deal. See also comment #1024. I’ll consider splitting it up though, that would probably make sense.

    Sorry about the the spambot issue, I’ll look into that. Might also want to blame your browser, I would think it should keep the text in there (Opera and Chrome seem to).

    Thanks so much for the suggestions!

  117. john Says:

    you are the best thank you deveria

  118. Jon Says:

    This is an oustanding resource. Alexis – I really appreciate your efforts here so thank you very much.

  119. drew Says:

    thanks, alexis. i’ve been hoping for a site like this for some time, and you’ve done it not only well, but beautifully too. i was directed here from Christopher Blizzard’s blog. Thanks again.

  120. HTML5 Says:

    Apple just released Safari 5.0 today, can you please test and see how is their standards support??

    http://www.apple.com/safari/

    http://www.apple.com/safari/download/

  121. Mike Plate Says:

    Thanks for a great reference page! I’m missing box-shadow though. Shouldn’t it be in the list?

  122. Magne Andersson Says:

    @Mike Plate: It is in the list, if you check the Unofficial/Note box at the top. Since it was removed from the CSS3 spec it can no longer be considered a Working Draft (or have any other status). It will probably make it into the spec again, though, in some other section.

  123. Thomas Barrasso Says:

    You should include browser specific methods to accomplish the equivalent task. For example, as much as I hate IE it has supported @font-face since 1999 via EOT, text and box shadows, RGBA (http://kilianvalkhof.com/2010/css-xhtml/how-to-use-rgba-in-ie/) and many other functions through the CSS filter property for quite some time as well.

  124. Juan Salcedo Says:

    HI Alexis,

    Great tool, congratulations!

    You know what would be cool? To mashup this with current browser market share info from
    http://en.wikipedia.org/wiki/Usage_share_of_web_browsers
    or
    http://www.w3schools.com/browsers/browsers_stats.asp

    So you could give some additional stat for the “Present” data in each item, that would say something like “Currently supported by % of the people’s browsers”.

    Contact me if I didn’t explain myself.

    Cheers,

    Juan Salcedo

  125. Richard Says:

    Where is CSS3 Ruby elements in de listing.
    That has been a Candidate recommendation specification for a long while.

  126. Pat Says:

    When will you add information for CSS3 opacity property? Thanks

  127. Fraser Pearce Says:

    Please please do a mobile edition of caniuse.com

    m.caniuse.com ;)

    F

  128. Alexis Deveria Says:

    Richard – Being considered, thanks for the suggestion.

    Pat – Not sure if just that property is worth adding by itself, but will think about it.

    Fraser – Great idea! Instead of creating a separate site, I’ve just set up some stylesheet rules for mobile devices. Does that meet your mobile needs?

  129. Fraser Pearce Says:

    Yes and know. Is certainly very cool, but clearly my request was vague and unclear.

    What I was aiming at was a whencaniuse for mobile browsers rather than desktop browsers. I.e. comparing iphone safari, android webview, opera mini, fennec, IE for Windows Mobile, etc.

    As a multi-platform developer, and with mobile devices forever becomig more common and thus more important for web development, I am finding it very hard to find a single clear source of web technology features that are supported by these browsers.

    Your site is above and beyond the best resource for such comparisons on a desktop browser engine level, but doesn’t cover mobile browsers.

    All this said, I appreciate that the mobile browser arena is chock full of variants of the same engine where features have been added or removed for various reasons, so it might make for a much more difficult list of features to ascertain and maintain.

  130. Alexis Deveria Says:

    Ah. Gotcha. Well, that does indeed become more challenging, though I understand how it would be useful. For now I would direct you to PPK’s mobile research and WebKit comparison if you’re not already familiar with it…while not all WCIU data is there, it may be of some use to you.

    In the future I may delve further into this, perhaps by letting visitors submit data and limiting the tables to the top most popular browsers. We’ll see. Thanks for the suggestion anyway.

  131. Magne Andersson Says:

    Work on implementing CSS3 3D Transforms in Firefox is being done (see https://bugzilla.mozilla.org/show_bug.cgi?id=505115) and it seems likely that it will make it in to Firefox 4.0.

  132. Magne Andersson Says:

    Oh, and your note about Safari only supporting CSS3 3D Transforms on Mac and iPhone, is now incorrect. Support has been added for Windows.

  133. Holger Says:

    very usefull page. Thanks!

    Please include HTML5 classList
    Firefox 3.6 has support, Webkit ist planing to support:

    https://developer.mozilla.org/en/DOM/element.classList
    https://bugs.webkit.org/show_bug.cgi?id=20709

  134. anon Says:

    details and summary html5 element are missing

  135. Louis Vuitton Says:

    This is an oustanding resource. Alexis – I really appreciate your efforts here so thank you very much.

  136. Louis Vuitton Says:

    Big thanks. Very much the helpful information!

  137. TT Says:

    Could you add an actual test which will show what browser currently used by visitor supporting?

  138. Peejong Says:

    Can I use ?
    CSS Namespaces
    (Candidate Recommendation)

  139. Jon Chappell Says:

    I know it’s impractical to add every single mobile browser version, but is there any chance you could at least support the latest versions of Mobile Safari for iPhone (iOS 4) and iPad (iOS 3.2)?

  140. PC Boxen Says:

    Wow this articel was amazing. Thanks a lot!

  141. Nathaniel Eliot Says:

    Masterfully designed, sir. You gave me exactly the information I was looking for when I started this search, ordered in exactly the way I wished it ordered. I can’t think of the last time I encountered a web app that did exactly what I wanted, without any tweaking.

  142. AMWJ Says:

    One feature of HTML5 I’m waiting for browsers to support is context menus, or . It would be very handy to have a built in right click context menu (without having to build it in ecmascript). Although it’s right there in the specs, no browser seems to have implemented them. Could context menus be added to the “When can I use” list?

  143. AMWJ Says:

    * or ‘menu type=”context”‘.

  144. Louis-Philippe Huberdeau Says:

    I would like to add emphasis on the fact that Chrome does not support offline applications. It is supported through gears, which is not available for all platforms. I believe Chrome was made available for Linux officially since version 6 or so, and it still does not support offline storage at version 10.

  145. Emil Loer Says:

    Great resource, thanks for all the hard work.
    Would you consider adding tests for the CSS3 units module? This covers things such as “vw”, “vh” and “rem” units, which can be used to specify dimensions.

  146. Vincent Scheib Says:

    Awesome, thx. Consider adding

  147. Vincent Scheib Says:

    Retry without html:
    DeviceOrientation
    http://dev.w3.org/geo/api/spec-source-orientation.html

  148. David Barrett-Kahn Says:

    This site is massively useful, thanks. Some features browser implementers have stated they will never support, like web SQL on firefox for example. I guess you could include that if you wanted to.

  149. Vincent Scheib Says:

    navigator.onLine would be nice to see too. kthxurgreat.

  150. Richard Says:

    It’d be awesome if you could show ‘dataset’ DOM attribute support. (I believe webkit has an implementation already). Otherwise, thank you for the site, very helpful! :)

  151. Athir Nuaimi Says:

    Now that Blackberry OS6 has a webkit browser, any chance this site will start to support it? It would be really great for those of us working on mobile sites.

    thanks

  152. Jeff Says:

    http://test.w3.org/webperf/specs/NavigationTiming/

  153. Jeff Says:

    http://www.w3.org/Submission/web-tracking-protection/

    (Both webtimings and webtracking protection are already supported in IE9)

  154. Caspar Lamy Says:

    Very useful and interesting site. But for partially support the color yellow should be used instead of dark-green. That would make it much more usable. I’m always thinking if light-green was partially and dark-green full support or otherwise. The traffic-light colors red/yellow/green would be best for not/partial/full support!

  155. TSS Says:

    Border image CSS consists of at least 6 elements.
    Firefox CSS 3.6 and 4.0 only supports 1 of those 6 elements.
    Should be listed as partial support and not full support.

  156. Adam Says:

    Can you remove the | from your URLs? e.g. http://caniuse.com/#compare=y&b1=firefox%7C3.6&b2=firefox%7C4It doesn’t work on some systems and can’t be posted in many forums as a link.

    Thanks!

  157. Joel Martin Says:

    web-socket-js (https://github.com/gimite/web-socket-js/) should be marked as a WebSockets polyfill for all browsers that support Flash.

  158. Gérard Talbot Says:

    Alexis Deveria,

    1- Can you add the percentage score of support for CSS 2.1 test suite for IE8, IE9, Konqueror 4.6.1 and Firefox 4 browsers into your “can I use…”
    compatibility tables ? This would be a lot more reliable, trustworthy, accurate, comparable and relevant than a cell with a bright green background. You could even do this for each section of the spec.

    2- Can you add Konqueror 4.6.1 (or 4.7 when it is released) in your compatibility tables?

    3- For ‘position: fixed’, ‘display: inline-block’, CSS min/max-width/height, CSS Table display, CSS Generated content, etc., I think it would be much better to present the percentage of success of passing tests from the CSS 2.1 test suite for these properties or for sections of the CSS 2.1 spec (much easier). And even here, you would have to state that the CSS 2.1 test suite is not entirely completed, over and done.

    4- As far as I can see, webkit-based browsers (Chrome 10, Safari 5) and Konqueror 4.5+ do not require the vendor prefix for box-sizing. Your compatibility table state the opposite.

    5- Overall, without comprehensive test suites to test respectively each and all of the properties and features, your compatibility tables have limited trustworthiness and relevance. It’s not enough to know that there is a support; it’s equally important to know how well it is supported and how correctly it is implemented and compliant with the spec.

    regards, Gérard Talbot

  159. Johan Sundström Says:

    It seems that getComputedStyle isn’t covered yet. It’s covered by all of Firefox (requires a 2nd “” or null arg prior to Firefox 4), Opera 7+, iCab 3+, Konqueror 3.5+, Chrome 3+, Safari 3+ and IE 9 in standards mode.

  160. nemo Says:

    The support for CSS as a background image has an important qualifier that isn’t represented on your test page.

    Animated SVG seems to only be correctly supported in Firefox 4 right now.

  161. _ck_ Says:

    Great work and very helpful!

    How about a column for Internet Explorer MOBILE ?

    http://en.wikipedia.org/wiki/Internet_Explorer_Mobile

    Versions 6, 7 and 9 exist and IE9 Mobile is supposedly very feature rich?

  162. Alexis Deveria Says:

    @anyone with feature suggestions:

    Thanks! No promises on which features I will add, but your requests are definitely noted.

    @those with corrections and link ideas:

    Thanks! Will update the information appropriately.

    @those who’d like to see more browsers/agents:

    For now I’m only able to add devices I can test myself (usually using an emulator) and they must have significant enough market share. I’d like to add BlackBerry next but have had trouble getting the emulator to work…

    @Adam – re: | in URLs, let me see what I can do.

    @Joel Martin – Thanks, will add!

    @Gérard Talbot –

    1, 3. Sounds like a good idea, I will consider this for the future. At the moment it’s not easy to make such a change though. Also note that the purpose of the site is to provide up to date rough ideas of whether or not a feature is supported for a very broad amount of features. Complete support analysis is not within its scope.

    2. Sorry, not enough user share. Statcounter gives the amount of global users as being less that 0.01%.

    4. You’re right about Chrome 10, has now been updated, thanks! Safari 5 however does not in my test.

    5. You’re absolutely right. But it appears evident that a “yes/almost/no” answer still has much value to designers/developers even if it can be inaccurate in different situations. For now, that’s the best I can do in order to cover as many features as I do.

  163. Jeff Says:

    http://www.w3.org/TR/2011/WD-css3-grid-layout-20110407/
    Supported by IE10 preview

  164. Roman Says:

    Please add Opera Mini 6.0 and Android 3.0 to the table.

  165. Necroman Says:

    You should add Safari 5.1 as “near future” for comparison – beta version is available in yet-to-be-finished Mac OS X 10.7 Lion

  166. Benjamin Says:

    Hello,

    i want to make a web application which will use much css3 and html5.
    in order to show the users the compatibility with the browsers it would be very cool if you could provide some kind of API.

    i would submit the features uses in my app and you could build such a nice and up to date compatibility table – with a “proudly presented by http://www.caniusehits.com” on the bottom.

    What do you think?

  167. Kaylie Says:

    You have shed a ray of sunshine into the forum. Tahkns!

  168. dobila Says:

    a very usefull tools, thanks.

  169. Luzifer Says:

    It would be nice if you could add mor SVG-related Stuff to your charts.

    At the moment i’m trying to build a website with SVG images referenced by the HTML “img” tag, which are styled by an external stylesheet referenced in the SVG’s.

    That way i’ve found out, that most of the browsers do that well, except for WebKit browsers, which allow only for one level of referencing documents. Thus, the first reference being the image itself in HTML, further referencing inside the SVG is blocked for some reason! So you cannot link externals stylesheets for SVG images embedded inside HTML in Safari or Chrome, or similar WebKit browsers! Works fine in Firefox, Opera, Internet Explorer (9+) …

    Please add at least external stylesheet referencing in SVGs inside Webpages to your charts, that would surely not only be helpful for me.

    I think most of the people are not really aware of this fantastic possibility and the power it gives your websites or applications, if that function would work properly!

  170. dave Says:

    Hi,
    awesome site!

    One thing is kinda strange:
    When I use the search field and after that try to follow a link form the index site it still shows the results of my initial search.
    Thats quite counter intuitive imho.

  171. Philip Peterson Says:

    Typed arrays?

  172. Temtem Says:

    Please also tell me where and when box-shadow:inset works! :)

  173. Brian Says:

    Excellent site! Thanks!

  174. Andylee Says:

    Opera Mini 6.1 and Opera mobile 11.1 are out already!

  175. a Says:

    svg’s getIntersectionList? thanx :)

  176. XBOX 360 Emulator Says:

    WOW, useful table! Thank you!

  177. Alexis Says:

    Really useful and well-rounded table. It could become even better if you added the Blackberry browsers.

  178. DigDug2k Says:

    I know we’re new on the block, and still trying to prove ourselves, but do you think you could include support for Firefox Mobile on the list? I can help fill in blanks if you need.

  179. Iraê Carvalho Says:

    Hi,

    I was researching the matchesSelector spec and it’s support. It’s well supported on latest browser versions, but is missed in past browser versions and in Opera it’s still nightly. I didn’t test for mobile support also.

    I thinks it’s a nice addition to “when can i use”. I made a link bundle with some references: http://bitly.com/pEQwWK

    Hope it helps!

  180. Alan Hogan Says:

    I would like to see the emergent HTML5 iframe attribute srcdoc documented here :)

  181. TSS Says:

    Official Ecmascript support test by Ecma interantional shows that IE 9 has 99.95% javascript support and chrome 12 about 95% support.

    Why is that not reflected in your scores where chrome sees to have better scores than IE.

    Why is caniuse.com results for javascript not in line with official javascript testsuite?

    Official W3C CSS testsuite also has IE9 outscoring clearly all other browsers in CSS 2.1 support.
    Why is caniuse.com contradicting the official W3C testsuite?

  182. FARKAS Máté Says:

    Please pick up the page-break[-inside] CSS2 property, too. It is very-very useful when pages are designed to printing, too, and it is specified in CSS2, and supported by Opera (and IE).

    See: http://www.w3.org/TR/CSS2/page.html#page-break-props

    Thank you very much for your great work!

  183. Martin Says:

    First of all, thanks for this great site!

    You know what would be awesome? If I could enter an URL and your page would then check what features it uses and so on… :)

  184. Kevin Says:

    Thanks for the hard work. Adding style@scoped to the chart would helpful for when somebody supports it.

  185. Elise Says:

    A suggestion – maybe include Blackberry Browser in the browser comparison?

  186. Leon Says:

    I love your site! It is incredibly helpful.

    Today, for the first time, I looked for a feature and it wasn’t listed on your site, the javascript Performance Timing and Navigation Timing features (window.performance), so I just thought I’d suggest adding them, although it looks like that may have been suggested already (by Jeff, March 12, 2011).

  187. Matthew Says:

    A couple updates for contenteditable:

    http://twitter.com/#!/rakaz/status/78716905648685056

    iOS 5 supports contenteditable.

Powered by Coffee, Marmite, jQuery and WordPress