Jump to content
Search Community

Scroll trigger for card to appear when scrolled

RADNM test
Moderator Tag

Recommended Posts

Hey guys Im finding trouble to get the cards appear(valueItemSection cards) when scroll triggers in that section.What i want to do is when valueSection is in the center of the screen and when user scrolls further the valueItemSection next card should appear and in the third scroll the last Item.Right now i have been able to pin the section to the center of the screen but im finding it difficult  to get Value Item cards on by appear on the screen. 

 const valueRef = useRef(null);
  useEffect(() => {
    const el = valueRef.current;
 
    const tl = gsap.timeline({
      scrollTrigger: {
        trigger: el,
        start: "top 20%",
        end: "+=1200px",
        pin: true,
        pinSpacing: true,
        markers: true,
        onEnter: () => {
          console.log("Enter");
          if (ScrollTrigger.isScrolling()) {
            console.log("Scrolling");
          }
        },
      },
    });
 
   
    return () => {
   
      tl.set("body", { overflow: "auto" });
      tl.kill();
    };
  }, []);
 
  return (
    <div className="container lg:mt-50 xl:mt-24 xs:mt-16 h-[100vw] ">
      <div
        className="text-center flex flex-col justify-center items-center"
        ref={valueRef}
      >
        <h4 className=" text-blue-50  font-normal ">LOREM IPSUM DOLOR</h4>
        <h3 className="text-black font-bold text-2xl lg:text-9 leading-7 lg:leading-10 mt-2">
          How We Add Value
        </h3>
        <p className=" text-gray-140 font-normal text-base leading-5 lg:leading-[1.21rem]  mt-6 lg:mt-4.5 sm:w-9/12 md:w-4/5 xl:w-[38rem] ">
          Lorem ipsum dolor sit amet consectetur. Placerat viverra id
          scelerisque quis sodales eget. Nam eget egestas urna id tempor amet
          vitae.
        </p>
        <div className="flex-row relative items-center justify-center gap-2 hidden lg:flex w-full mt-4 mb-4">
          {Data.tabs.map((chip, index) => (
            <ValueTab
              key={index}
              icon={chip.icon}
              title={chip.title}
              active={true}
            />
          ))}
        </div>
        {/* Desktop view */}
        <div className="relative w-full hidden lg:flex flex-col gap-5 ">
          <ValueItemSection
            title={Data.items[0].title}
            description={Data.items[0].description}
            icon={Data.tabs[0].icon}
            chips={Data.items[0].chips}
          />
          <ValueItemSection
            title={Data.items[0].title}
            description={Data.items[0].description}
            icon={Data.tabs[0].icon}
            chips={Data.items[0].chips}
 
          />
        </div>
        <div className="relative w-full flex flex-col gap-5 lg:hidden ">
          {/* Mobile view */}
          {Data.items.map((item, index) => (
            <ValueItemSection
              key={index}
              title={item.title}
              description={item.description}
              icon={Data.tabs[index].icon}
              chips={item.chips}
            />
          ))}
        </div>
      </div>
    </div>
Link to comment
Share on other sites

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: 

 

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. 

  • Like 1
Link to comment
Share on other sites

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. 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...