Opera Mobile not treated as A grade (transitions) #1883
Comments
Was just going to file a ticket, but I see Paul beat me to it. Are there any issues with Opera transitions, or was this code just taken from jQTouch? |
Also since FF Mobile is A-Grade and I assume WP7 Mango will be, we might as well go for the full 4 prefixes plus standard unprefixed. Futureproof! |
Thanks for the reminder guys. The transitions are tweaked versions of jQTouch so they only have WebKit rules right now. We plan on adding a lot more CSS support for other platforms so this is good timing. Note that Opera Mini, not Mobile, is opted out fo the Ajax navigation for a number of reasons so it will just get the build-in slide transition. We haven't dug into Opera transitions to know how good the support is on Mobile, but this is on deck for Beta 2. |
Looking at the code for This is the approach that Modernizr takes. (I guess that means that |
Oh, overlooked that you've got |
Ok, so the decision was made to wait a bit before moving to transitions because both Opera and Firefox mobile don't have a good level of support (yet). We plan on moving to transitions to support these browsers post-1.0. |
Moving to the feature request wiki since we'll be adding this post-1.0: |
though the site indicates opera mobile gets a grade support, the code currently only considers css transition support in webkit, but not opera.
the functionality of
Modernizr.prefixed()
could be leveraged to determine if you need a webkit or opera prefixed and choose the appropriatetransitionend
event.The text was updated successfully, but these errors were encountered: