Vấn đề rung lắc của Element trên thiết bị ios – GSAP

Hi,

There are a couple of issues in your demo, first use our useGSAP hook because 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/

Using the hook will ensure that the DOM is properly rendered so you don’t have to resort to that timeout you’re using in your code.

But I think that the issue lies here:

gsap.to(elementToMove, 
  x: 0, // Start with no offset
  ease: 'none',
  scrollTrigger: 
    trigger: container,
    start: 'top bottom-=10%', // Start the animation when the top of the container is 5% from the bottom of the viewport
    end: 'top top-=25%', // End the animation slightly above the top of the viewport
    scrub: true,
    ease: 'none',
    onUpdate: (self) => 
      const progress = self.progress; // Use progress directly (0 to 1)
      const currentXValue = -progress * xValue; // Calculate the current position based on progress
      gsap.set(elementToMove,  x: currentXValue ); // Apply calculated x position
    ,
  ,
);

That onUpdate callback is basically moving the same element ScrollTrigger is animating and on the same property, if you want to move elements horizontally just use the configuration in the Tween to move the entire container and not an onUpdate callback on ScrollTrigger, seems overkill and wasteful IMHO. Something like this:

See the Pen vYodaeo by GreenSock (@GreenSock) on CodePen

Hopefully this helps

Happy Tweening!