Soh8

@Cassie Indeed it might not be necessary for my case ! At first by using it, I thought it would do no harm and prevent eventual issues... But I guess that if it was necessary, I would encounter the scroll issue anyway by using the normalizeScroll option anyway. To see what I mean exactly, I think the best way to understand the issue would be to get an ipad and visit your scrollsmoother page: https://greensock.com/scrollsmoother/. If you don't see any issue, then ignore my message, maybe it's just my ipad. - ipad pro 2021, issue in safari & chrome

@grizhlie Thanks, thanks to you I realized that "normalizeScroll: false" was messing up the scroll on mobile devices in one of my projects. @GreenSock I think this should be either fixed or mentioned in the doc. Even on the https://greensock.com/scrollsmoother/ page, I have that issue on iPad where it's really buggy when I scroll. Somehow normalizeScroll seems to mess it up on touch devices.

Well, thanks a lot ! And I didn't even need the nested timeline, just wrapping the gsap.to() into the function worked and it seems to be flawless so far. I just went from this to this: // Went from this timeline.add( gsap.to(el.current, { duration: 1, opacity: 1, ease: 'power3.easeOut' }) ) // To this timeline.add( function() { gsap.to(el.current, { duration: 1, opacity: 1, ease: 'power3.easeOut' }) } )

Wait sorry @mvaneijgen I think your solution is the way to go actually. I didn't get it at first. But by wrapping it into the function you kind of trigger the animation at the right time but get it out of the queue ?? What's the magic here

Thanks @mvaneijgen. This is not quite where I want to go. I'll try to explain my real world issue deeper: I have multiple components that adds animation to my master timeline. During the lifecycle of the application, some component are used, some don't. So, some animations are added, some are not. Then finally, I play the master timeline. -> So the important thing here is that it means that I do not always end up with the same set of animations before playing the master timeline. One of the animation (the second one in my example) needs to run after another (the 1st one in the example), but when triggered, should not impact the next one (the 3rd one in my example) I can't use the position parameter on the "next" animation because sometimes, the 2nd animation will not be added to the master timeline. To illustrate this on my example: If I would use the position parameter on the 3rd animation, but do not add the 2nd animation, then the position parameter of the third animation would affect the 1st animation. And that's what I want to avoid. Thanks !

Hello ! In a timeline, I'd like to control the start of the next animation from my current animation function: const timeline = gsap.timeline() timeline.add( gsap.to('.rect', { x: 100, }) ) timeline.add( gsap.to('.rect', { opacity: 0.5, }) // I want this call to start after the previous one // but also to have no effect on the // start time of the next animation below ) timeline.add( gsap.to('.rect', { y: 100, }) ) Is that possible somehow ? One obvious option would be to change the position parameter of the last add() call, but I'd like to avoid that if possible because in the context of my application, I have no direct access to that last add() call. Thanks !