add support for Opera transitions #4521
Comments
I can confirm this issue. The console shows an error in jQuery: Unhandled DOMException: SYNTAX_ERR jQuery 1.7.1 line 5071 / 1.7.2 line 5163
Besides Dragonfly shows hundreds of "unknown property" errors in CSS |
Confirmed. Same issue on opera 12 |
Confirmed. Same issue, opera build 1467 upgrade. Sites like chat.stackoverflow.com don't render at all. Same exception Unhandled DOMException: SYNTAX_ERR |
OK, that took a little bit to wrap my head around due to a Dragonfly setting (Settings > Scripts > Show Parse Errors and Break on Exceptions, trying to get that to default to off, but that's another story). The actual issue seems to be two-fold: lack of Let me quote from internal discussion for more context:
I've just confirmed locally that this does in fact fix the page-goes-blank problem. Thanks for the heads up and sorry for the confusion. |
For reference: #1883 |
Are there any fixes planned? |
Update: changed the topic of the issue |
The event type has been changed from |
Transitions doesn't work yet on Opera because it doesn't support 3D transforms. Let's reopen when this is supported. |
So you need to have 3d transforms to get any transition? Weird. |
@miketaylr - we use 3D support internally as a less-than-ideal diagnostic of a browser's ability to run complex animations smoothly. We introduced this as a way to kick poorly performing platforms like Android 2.x or WebOS from blinking and generally freaking out when attempting (and failing) to run transitions, even relatively simple 2D ones like slide or pop. When 3D isn't supported, we kick in a fallback mechanism and default to showing a simple fade transitions which most platforms seem to do a decent job with. All of this is configurable, but these are the defaults. If Opera mobile doesn't support 3D animations, it's probably not worth adding all this code. If you're moving soon to non-prefixed keyframe animations, I'd rather add those and gain both Opera and IE10 support with one set of properties. What do you think? |
I disabled the 3D-transforms support check to test the transitions on Opera desktop and I have to say they animate far less smooth then on Chrome and Firefox. That includes the "fade" transition. Only exception is "slide" which looks good. The "flip" and "turn" transitions don't work. If you like you can pull |
@jaspermdegroot after two years I think you should reconsider to include Opera in 3d transitions again. I have just tried to run all the transitions by using the standard demo site (http://demos.jquerymobile.com/1.4.5/transitions/) and I my eyes it looks good. I havn't tryied OperaMini. While reviewing the transform3dTest you should also consider to change from: to: if ( ret ) { |
Thanks for the pointer. Actually it is included already and transitions work on Opera and Opera Mobile. Opera Mini doesn't support 3D transitions. |
Actually |
While checking the JQM doc pages ('1.1.0' or 'test') on Opera 12 I found that navigating to another page shows an empty page (then a click on the browser back button shows another empty page). If the destination page is reloaded though it shows the page correctly.
When the first page loads, the "Scripts" developer panel shows a :
in jquery code with this call stack (sorry minified code there):
m jquery-1.7.1.min.js:3
a.find jquery.mobile-1.1.0.min.js:25
find jquery-1.7.1.min.js:3
a.mobile.focusPage jquery.mobile-1.1.0.min.js:51
jquery.mobile-1.1.0.min.js:40
jquery.mobile-1.1.0.min.js:41
f jquery.mobile-1.1.0.min.js:42
a.mobile.changePage jquery.mobile-1.1.0.min.js:63
initializePage jquery.mobile-1.1.0.min.js:175
jquery.mobile-1.1.0.min.js:176
f.Callbacks jquery-1.7.1.min.js:2
fireWith jquery-1.7.1.min.js:2
ready jquery-1.7.1.min.js:2
B jquery-1.7.1.min.js:2
Maybe this is not related to the above navigation problem by the way..
Not sure if that's a jquery problem, a JQM one or Opera..
Tested using Opera 12.00 Build 1467 for Linux (Opera Turbo Off and On : same problem).
Update: Problem not reproduced in opera 12 mobile on Android ICS.
The text was updated successfully, but these errors were encountered: