Horizontal scroll instantly jumps to end value on trigger

[rdawg365]

I have a section #about, then a child container element #about-container that I want to give a horizontal scroll. However, when #about-container hits it's scroll trigger, #about translatesY down to the trigger's end value. So let's say if the end value is 6000px, #about will instantly jump down 6000px. This makes it appear like it's disappearing from the screen. What's more, when I scroll up, the translateY value on #about seems to revert to what it should be. How do I fix this behavior? For more context, this is one section on a page that has ScrollSmoother applied so I have to use pinType transform over position:fixed.

 

I've attached a codepen link, but I can't get the React/Tailwind/GSAP stack to render properly. You'll still be able to see the set-up though.

See the Pen Exzoqjy by rdawg3000 (@rdawg3000) on CodePen

[GSAP Helper]

Hi there! I see you're using React -

Proper cleanup is very important with frameworks, but especially with React. React 18 runs in strict mode locally by default which causes your useEffect() and useLayoutEffect() to get called TWICE.

 

Since GSAP 3.12, we have the useGSAP() hook (the NPM package is here) that simplifies creating and cleaning up animations in React (including Next, Remix, etc). It's a drop-in replacement for useEffect()/useLayoutEffect(). All the GSAP-related objects (animations, ScrollTriggers, etc.) created while the function executes get collected and then reverted when the hook gets torn down.

 

Here is how it works:

const container = useRef(); // the root level element of your component (for scoping selector text which is optional)

useGSAP(() => {
  // gsap code here...
}, { dependencies: [endX], scope: container }); // config object offers maximum flexibility

Or if you prefer, you can use the same method signature as useEffect():

useGSAP(() => {
  // gsap code here...
}, [endX]); // simple dependency Array setup like useEffect()

This pattern follows React's best practices.

 

We strongly recommend reading the React guide we've put together at https://gsap.com/resources/React/

 

If you still need help, here's a React starter template that you can fork to create a minimal demo illustrating whatever issue you're running into. Post a link to your fork back here and we'd be happy to take a peek and answer any GSAP-related questions you have. Just use simple colored <div> elements in your demo; no need to recreate your whole project with client artwork, etc. The simpler the better. 

[rdawg365]

Switching from useEffect to useGSAP indeed solved the issue!