Yeah, the crux of the problem is that most modern browsers handle scrolling on a totally different thread which is super annoying in cases like this because you CANNOT synchronize things. So ScrollTrigger is accurately setting the transform values to make the element appear "stuck" (fixed) but the browser is moving the WHOLE page for the scroll briefly before it renders the changes that ScrollTrigger made via the main JS thread.    One thing that could solve this in your case is to use
    • Thanks
    • Like
    3