Hey guys, I'm new to GSAP, and the problem I'm facing is that my second ScrollTrigger is not working. However, if I remove the first animation, the second one works perfectly. Can you help me fix this issue?

[Eduardas]

const BringSection = () => {

  const rightRef = useRef(null);

  const sectionRef = useRef(null);

  useEffect(() => {

    gsap.registerPlugin(ScrollTrigger);

 

    const ctx = gsap.context(() => {

      gsap.fromTo(

        sectionRef.current,

        {

          y: 200,

          opacity: 0,

        },

        {

          y: 0,

          scale: 1,

          opacity: 1,

          duration: 1,

          scrollTrigger: {

            trigger: sectionRef.current,

            start: "top bottom",

            end: "top center",

            markers: true,

          },

        }

      );

 

      ScrollTrigger.create({

        trigger: ".gallery",

        start: "top top",

        end: "bottom bottom",

        pin: rightRef.current,

        markers: true,

      });

    });

 

    return () => ctx.revert();

  }, []);

 

  return (

    <section

      ref={sectionRef}

      className="bg-gray-300 rounded-[4rem] section-reveal"

    >

      <div className="gallery">

        <div ref={rightRef} className="right">

          <div className="photos">

            <div className="photo red"></div>

            <div className="photo green"></div>

            <div className="photo blue"></div>

          </div>

        </div>

        <div className="left">

          <div className="detailsWrapper">

            <div className="details">

              <div className="headline red"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

            </div>

 

            <div className="details">

              <div className="headline green"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

            </div>

 

            <div className="details">

              <div className="headline blue"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

              <div className="text"></div>

            </div>

          </div>

        </div>

      </div>

    </section>

  );

};

 

export default BringSection;

[GSAP Helper]

Without a minimal demo, it's very difficult to troubleshoot; the issue could be caused by CSS, markup, a third party library, a 3rd party script, etc. Would you please provide a very simple CodePen or Stackblitz that illustrates the issue? 

 

Please don't include your whole project. Just some colored <div> elements and the GSAP code is best. See if you can recreate the issue with as few dependencies as possible. Start minimal and then incrementally add code bit by bit until it breaks. Usually people solve their own issues during this process! If not, at least we have a reduced test case which greatly increases your chances of getting a relevant answer.

 

See the Pen aYYOdN by GreenSock (@GreenSock) on CodePen.

that loads all the plugins. Just click "fork" at the bottom right and make your minimal demo: 

 

Using a framework/library like React, Vue, Next, etc.? 

CodePen isn't always ideal for these tools, so here are some Stackblitz starter templates that you can fork and import the gsap-trial NPM package for using any of the bonus plugins: 

• React (please read this article!)
• Next
• Svelte
• Sveltekit
• Vue
• Nuxt

 

Please share the StackBlitz link directly to the file in question (where you've put the GSAP code) so we don't need to hunt through all the files. 

 

Once we see an isolated demo, we'll do our best to jump in and help with your GSAP-specific questions. ✅

[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. 

[Eduardas]

https://stackblitz.com/edit/stackblitz-starters-p7xpus?file=app%2Fpage.tsx

When the commented-out part is included, you can see how it is supposed to work. However, when the code part is uncommented and an extra animation is added, it breaks. Can you help fix this issue?

[Cassie]

Heya!

 

So this is a pretty tricky situation you've laid out. You're transforming the parent on the y axis, and at the same time, trying to pin a container inside it.

 

Two issues here

 

1) Your positioning calculations are going to be off because you're moving the container on the y axis

2) You're then trying to pin an element with position 'fixed' inside a transformed container - position fixed doesn't work in a pinned container

 

You can kinda fudge your way around by changing to pinType "transform" and making sure to refresh your triggers when the initial 'fade in' animation plays. BUT honestly, if I were you, I would just refactor my demo so that the container isn't moving on the y axis. You could create the same effect by just moving children of the container instead and avoid all the issues.

 

See the Pen qBzdNNB?editors=0010 by GreenSock (@GreenSock) on CodePen.

 

Hope this helps!

[Eduardas]

Thanks, that fixed my issue. However, instead of using pinType: transform, I used pinReparent: true because when I scrolled with pinType: transform, I could see the div shaking weirdly.  Because I'm also using SmoothScroll from Lenis.