iOS acceleration #9
Conversation
| Move.prototype.setVendorProperty = function(prop, val, options){ | ||
| if ((!options) || (!options.noWebkit)) { | ||
| this.setProperty('-webkit-' + prop, val); | ||
| } |
There was a problem hiding this comment.
options = options || {};
if (!options.noWebkit){
would be easier to read
|
@visionmedia, do you plan to include this pull request? That fixs a problem ( suddenly, browser shows white screen ) when using continue animations on mobile devices. Tested on ipad2. |
|
i'll try it in a min, alot of the PRs have been breaking stuff |
|
cant get it to apply cleanly |
|
Has this been completed now? |
|
@jrok, i don't know, but if it does not fit your case, you could also give a try to jquery.transit. |
|
Yeah, working with jquery transit now, was hoping to use move.js instead as its a little less complex. Caveat i guess is that its also a little less functional...thanks |
|
@rstacruz I'd be happy to give you commit access to this repo if you want, too many projects now :D |
|
+1 |
This makes move.js do hardware-accelerated transformations and scales on iOS devices.
This uses
-webkit-transform: translate3d()andscale3d()in addition totranslate()andscale().One caveat:
move().x(40).y(40)will now not produce the correct result. This will do add twotranslate3d's to the-webkit-transformproperty. This can be fixed, but I'm not sure on the cleanest way to do that right now...