Browser support for HTML5 & CSS with Modernizr 1.5
We proud to announce the relaunch of the Web Designers HTML5 & CSS3 browser support checklist, now using Modernizr 1.5 for even more tests and improved accuracy.
-
Browser Support for SVG and more
It's been a couple of weeks now since Modernizr 1.5 was released and we've been inundated with requests to update our Litmus test page which shows browser "support" for CSS3 and the HTML5 family of technologies.
Well now it's finally here and we're pleased to re-launch the Web Designers Browser Support Checklist with tests for:
- HTML5 Web Applications
- HTML5 Embedded Content
- HTML5 Audio & Video
- HTML5 Web Forms & Attributes
- CSS3 Properties
- CSS3 Selectors
New tests for SVG, Web Sockets and much more
Thanks to the guys over at Modernizr, we can now provide test results for a wide variety of new features including the long awaited SVG tests (I'm sure Bruce Lawson will be happy at that!).
The full list includes:
- SVG (including SVG Clipping Paths and SMIL)
- Web SQL Database
- IndexedDB
- Web Sockets
- hashchange event
- History and Session Management
- HTML5 Drag and Drop
- Cross-document Messaging
Even Better Accuracy
Know how import it is that our results are accurate and so we're really pleased that the Modernizr library we rely on to produce our results is becoming increasingly bug free.
The issues with Font Face in WebKit have now gone and we're now seeing more accurate results for basic CSS3 properties such as border-radius which is fantastic.
On top of this our developers have spent a lot of time rewriting the site code in an attempt to reduce the likelihood of false results being returned from our end so hopefully our results should be more accurate than ever.
What we don't offer
We'd like to make it clear that the results we provide as only a summary of browser support for HTML5 and CSS3. We strongly recommend you test you code fully to ensure that you get the expected results.
We also don't test for every last feature or browser idiosyncrasy. Beware! Browser manufacturers implement the spec in different and occasionally buggy ways. Again, we strongly recommend testing - there really is no substitute.
Provide us with feedback....please!
We really need your help to make FindMeByIP 100% accurate. If you notice a bug just let us know. You can reach us either by:
- Commenting on this post (preferred)
- Twitter - @deepbluetweets
Just let us know the error, where it's appearing and which browser and we'll make a temporary fix immediately.
Then as soon as we have a spare moment on Friday our developers will fix the root cause to avoid the issue creeping back in.
We really hope you find these tables useful.
6 Comments on this post
Speak to an Expert now on 01225 444 674
Talk to Us
Juan said “Thanks” earlier this year
Martin said “Opera 10.60” earlier this year
Christian said “IP-Location should be better” earlier this year
Jim said “@Christian - IP Location” earlier this year
Christian said “inaccurate location data” earlier this year
Jordi said “Useful” last week