HTML5 compatibility on mobile and tablet browsers(mobilehtml5.org)
mobilehtml5.org
HTML5 compatibility on mobile and tablet browsers
http://mobilehtml5.org/
7 comments
I appreciate getting support information out there but don't take "supported" to mean "always works as expected". The primary example here is position fixed support which is _extremely_ broken in Android 3.1-4.0 on orientation change.
I agree - lists like these don't really have value if you're doing serious mobile web development. A few more examples of broken and inconsistent implementations:
• Viewport - this meta tag isn't supported on HTC phones, so your slick CSS media queries will expose a terrible UI in some cases.
• Websockets - the specification was changed after vendors implemented it, so you have to support multiple authentication schemes on the server side.
• Video - every vendor has their own take on how the controls should look, and certain vendors (I'm looking at you, iOS) disable or override the w3c default specification, so you have to sniff user agents to make a decent custom control. That's not to mention the difficulty of supporting all the various formats.
What adds to the pain is that the browser vendors don't always do a great job of keeping their APIs current, so you have to play the trial-and-error game to tease out the reasons you're having trouble - a game that is exceptionally difficult when the problem only occurs on the mobile device itself.
• Viewport - this meta tag isn't supported on HTC phones, so your slick CSS media queries will expose a terrible UI in some cases.
• Websockets - the specification was changed after vendors implemented it, so you have to support multiple authentication schemes on the server side.
• Video - every vendor has their own take on how the controls should look, and certain vendors (I'm looking at you, iOS) disable or override the w3c default specification, so you have to sniff user agents to make a decent custom control. That's not to mention the difficulty of supporting all the various formats.
What adds to the pain is that the browser vendors don't always do a great job of keeping their APIs current, so you have to play the trial-and-error game to tease out the reasons you're having trouble - a game that is exceptionally difficult when the problem only occurs on the mobile device itself.
That's exactly what I came here to say.
Android 'supports' CSS transforms, but a bug in Android 2.2+ (works fine in 1.9) means that you can't apply more than one simultaneous transition to a single element at a time (I don't know if this has been fixed in more recent versions, but it's still a big backwards compatibility issue).
iOS MobileSafari supports 'multimedia' (and is listed as such), but it's not until iOS 6 lands that we're getting proper Web Audio API support to actually provide a non-hacky way of playing sound for uses like games that require precise timing.
A binary yes/no really doesn't encapsulate the subtlety and complexity of mobile feature support.
Android 'supports' CSS transforms, but a bug in Android 2.2+ (works fine in 1.9) means that you can't apply more than one simultaneous transition to a single element at a time (I don't know if this has been fixed in more recent versions, but it's still a big backwards compatibility issue).
iOS MobileSafari supports 'multimedia' (and is listed as such), but it's not until iOS 6 lands that we're getting proper Web Audio API support to actually provide a non-hacky way of playing sound for uses like games that require precise timing.
A binary yes/no really doesn't encapsulate the subtlety and complexity of mobile feature support.
WebSQL should not be used under any circumstances. Instead use IndexedDB with this shim: http://nparashuram.com/IndexedDBShim/
Also, Chrome support for IndexedDB should have an asterisks as it implements an outdated version of the spec.
Also, Chrome support for IndexedDB should have an asterisks as it implements an outdated version of the spec.
"Don't use WebSQL, use IndexedDB. It doesn't work correctly in Chrome."
Don't get me wrong, I know what you're saying and why. Just the juxtaposition of the two statements is noteworthy.
Don't get me wrong, I know what you're saying and why. Just the juxtaposition of the two statements is noteworthy.
You can shim WebKit to use onupgradeneeded, https://github.com/matthewp/multientry-shim/blob/master/upgr...
There are still a few other things that it won't do (multiEntry, Blob storage to name a couple).
There are still a few other things that it won't do (multiEntry, Blob storage to name a couple).
The logo and share icons don't move with the horizontal scrollbar. Ouch.
Edit: The colouring of the column headers messes with my eyes. They ignore the white and focus on the gray.
Edit 2: position: fixed is hardly HTML5, even if it's something quite a few mobile browsers didn't support in the past.
Edit: The colouring of the column headers messes with my eyes. They ignore the white and focus on the gray.
Edit 2: position: fixed is hardly HTML5, even if it's something quite a few mobile browsers didn't support in the past.
Always using feature detection isn't feasible, some features can't be detected.
https://github.com/Modernizr/Modernizr/wiki/Undetectables
https://github.com/Modernizr/Modernizr/wiki/Undetectables
Interesting information but whatever they were trying to do with the HTML5 logo ruins the experience.
is there a similar list for regular desktop browsers, i.e. non-mobile ?
Found one - http://caniuse.com/
(Disclosure: I'm a mobile Firefox developer.)