pederan

I was using v 1.661, and by swapping to v 1.8.2 fixed this issue with different top value. I also noticed that if I use bottom value it calculates the correct top value in the latest version Thanks a lot for all help, keep up the good work.

Hi Ok, sounds great. But why doesn't the inline top value set by TweenMax differ from the top value set in my css class? You can see from the screenshot that top is set to -0.05px by gsap while top is set to 140px in my css class. This messes up the layout unless I declare my top value as important. Shouldn't gsap set the inline top property to the same value as defined in my css class +- 0.05px?

Yes, that certainly clears things up and explains why the value is added, thanks. I noticed this in my latest project where I had position an element by the bottom property, and the position was all wrong in FF. The inline top property that is added overrided the bottom property in my css class. I then changed the bottom property to a top property in my css and positioned it as earlier. But that didn't solve it either since the inline top value was set to 0px and the value in my class was something else. I solved this by adding the !important declaration to it. But I guess this can cause the bug you mentioned to kick in since the top value in the inline style is ignored?

Hi Are you aware of that css top property is added to tranform tweens in Firefox? For a translateX tween (which is converted to matrix()) the top value from css is added to the inline style attribute. It seems this only happens in Firefox (not safari, chrome and opera) Check out this codepen: http://codepen.io/pederan/pen/IsLpe Here top: 20px is added as inline style And even stranger if you add translateZ(0.1px), 0.05px is added to the the applied css top value Check out this codepen: http://codepen.io/pederan/pen/mfour Here top: 40.05px is added as inline style at tween end. Also it looks like the matrix values are tweened/updated after the tween is complete. This is highly undesired behaviour and I guess it also affects the performance in FF. Anyone know why this is happening? Regards Peder