annarack

Perfect, thanks a lot @GreenSock! Any idea on when the next release is going to happen? I was just confused on why its not working when applied to the parent, so I also tried the child version. But makes total sense why its not behaving how it should there. Thanks!

Hi @Rodrigo, thanks for your response! Sorry I guess I wasn't clear enough there. The problem is that I want the child elements to behave the same regarding the fade in and out. So they should fade in at the same positions at the bottom and out towards the top of the screen. But they should have different speeds. At the moment the fade in and out happens at he wrong time as soon as I add the data-speed property. For example if I add the data-speed property to the wrapped element which is also used for the scrollTrigger, it fades in more or less correctly but out already at the middle of the screen. The latest version of ScrollTrigger didn't make a difference to that on my side.

Hey guys! First thanks for your amazing work I'm currently working on a project which is kind of a scrollytelling website, done with React+NextJS and I decided to go with GSAP for the animations. I'm not sure if I missed that in the docs, but I currently struggle with a problem that feels quite basic. I'm building different components to reuse and one of them is a "FadeInOut" wrapper-component, that should fade in its children when scrolling in view and fading out when leaving. The problem appears as soon as I want to add different data-speeds in addition (Tried it on triggered element itself and child). Seems like the start/end positions of the fade scrollTrigger are not taking in account the offset of data-speed...or somehow get calculated wrong. What am I missing? Thanks in advance!