Fyrdility

I have added a new mode of displaying feature support information on “When Can I Use” resulting in the ability to select two browsers and only see what the differences are in feature support.

This allows you to pit two different browsers against each other to see which one outdoes which in what areas, but it is also useful to get a quick overview on which new features can be used in an upcoming release. For example, selecting Chrome 1 and 2 will let you see which new features are now available in Chrome 2.

This new mode will also tell you how much better one browser version is than another, note this is highly unscientific and doesn’t take into account support of features not mentioned on When Can I Use. Still, it’s kind of entertaining. Also, the mode generates URLs from your selection, so feel free to share your results with others.

Currently it only shows differences in support, I plan on also providing the option of displaying support common in both versions, as well as missing support. There may be a few other rough edges that need fixing, please let me know if you see anything that looks odd.

There may be a better information source, but I just noticed a photo from the Gizmodo iPhone OS 3.0 coverage, which at the top right includes “Audio/Video tags“. Unless I’m very much mistaken, this refers to the HTML5 elements being supported in Safari!

This would be my #1 wish in my recent wish list, so if true and supported properly, it could be awesome.

Here’s a list of things I’d like to see webkit for Mobile Safari to support. The browser currently meets a lot of my web-app needs, but I want more! And yes, I could just write my own real apps, but I’d prefer a way for developers to make things without having to pay for the privilege to do so. So here’s what I’m looking for:
(more…)

An update to the “When can I use” page, now you can filter by spec status. This is helpful to only see support for full W3 recommendations, mostly stable specs, features still in flux or completely unofficial features.

I find it interesting to see that with IE8 Microsoft has focused largely on improving items under “candidate recommendation” status (primarily CSS 2.1), whereas most full recommendations (XHTML, SVG, MathML) get ignored. Working draft features seem to only be added when the spec is pretty clear cut, such as the querySelector one.
(more…)