morekid

Ah interesting thanks, appreciate all the info. That works indeed, although in theory I would have imagined the gsap properties to be equivalent to their css counterparts. Will be using gsap ones from now on and hopefully I should see more consistent behaviour then. I have CSS defaults for my transforms so that the page can be consumed statically, ideally I'd want to be able to always have that as a fallback. So perhaps I'd expect to configure this kind of behaviour in gsap. For instance using some kind of layering property to indicate whether to replace CSS rules entirely or stack gsap ones on top of them.

Hi, I'm struggling to make gsap behave consistently across browsers when applying multiple translations, Firefox especially is treating the same transform values entirely differently from Chrome/Safari. I need both relative and absolute values in order to achieve the transition I'm after. I've also noticed that when applying a transform using "x", "y" directly it will erratically either override or add to a pre-existing CSS rule. See the linked pen, perhaps I'm missing something on how I'm handling this.