tronyx

Thanks for the response, Jack. Yup, seems like 1.18.4 will fix both problems! Looking forward to it!

Yes, there is a problem with perspective property if it is a number and not a string. In 1.18.3 that property is applied, but if I set numeric value of 70, it will apply css value of 700px. Also, what I'm trying to point to, there is a second problem, maybe connected to first one. If you look at my two previous examples, I have set perspective property as a string in both, and when I inspect code perspective have a value of 70px. So far soo good. But in 1.18.3 rotated element have following property: matrix3d(1.2, 0, 0, 0, 0, 0.848528, 0.848528, 0, 0, -0.707107, 0.707107, 0, -11.9098, 9.27076, 0, 1) and in 1.18.2 (which is correct) matrix3d(1.2, 0, 0, 0, 0, 0.848528, 0.848528, 0, 0, -0.707107, 0.707107, 0, 0, 0, 0, 1) I hope that now is more clear. Also, sorry for my bad English

Ah, thank you very much, great answer! I will keep that in mind! Though again, I am not sure how that actually works fine with 1.18.2 in every browser, even in IE10 Here is the same code with 1.18.2 http://codepen.io/anon/pen/QNVBPw

Hi Jonathan, thank you for your quick response. Sadly, this soution works on previous example, but on real code it doesn't. Here I have created real problem, with 1.18.3 and using string as a prespective value. http://codepen.io/anon/pen/QNVrdE If I use numeric value it still has a bug, but somehow different. If I use 1.18.2, no matter which value I set for perspective (numeric or string) it works perfectly fine. I'm still not sure if that's some bigger bug or I'm doing something wrong, but in 1.18.2 works just fine

Hi, I have a problem with a version 1.18.3 Here is a codepen with 1.18.3 in action http://codepen.io/anon/pen/PNdQdO and here is a same code with 1.18.2 in action http://codepen.io/anon/pen/reZJKE First I have tried to fix my code, which was working before and later i have realized that I have updated TweenMax version. After switching to 1.18.2 everything works fine as before. Is something changed so I need to change my code or this is a bug? Thanks!