Hi Greensock,
Thanks for your quick answer, my reply is somewhat late, sorry
Quote from that thread:
I agree, if you do want to analyze the element's size on every update. And analyzing and converting to a absolute value is no effort before start animating.
1.
With Chrome I meant both Chrome on desktop and on Android. The HTC One (and ony Xperia Z1) I tested it on are recent, high-end devices. I assume they are not that slow..(?)
2.
I'm animating 5 small elements (60px, 2 times X, Y, scale difference. 3 times only the X is different), 2 opacity's for full screen div's and 1 or some more elements sliding in.
3. Is force3d:true a substitute for adding a e.g. z;0.1 value ? So instead of { x:, y:, z:, scaleX:, scaleY, scaleZ } I can set a force3d:true and use { x:, y: scaleX, scaleY } ? Not setting the scaleZ gives me aan combined animationm, with scaleZ I get a matrix. Is there a difference in performance between a combined "translate3d(x, y, z); scale(x, y)" and a "matrix3d(..,..,..,..,..)" ?
3.1.
Using force3d:true, whould that kill the downgrade to animating left, top for not 3d animation supporting browsers?
Thanks!