GSAP ScrollTrigger Consecutive Flip

[DaphneHeraizBekkis.Bolk]

Hello gsap-community,

I  have a problem with GSAP scrolltrigger consecutive flip.
I created a loom here https://www.loom.com/share/592a2f60b84547d7912da965fae61440?sid=b8824d73-e552-4770-aec6-56824a5172e4 to explain the issue. And here are the links :

- Unique test : https://client-sites-debug.webflow.io/ without additional code

- Stagging site : https://hubcycle.webflow.io/expertise with additional scripts

 

I am so lost, I tried many things and combinations but it is so random.

I got my inspiration from that  a bit of ChatGPT and of me.

 

Thank you for you help in advance!

See the Pen myejmZO by D_HB (@D_HB) on CodePen.

[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 GSAP as shown in the Install Helper in our Learning Center : 

• 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]

Yeah, we really need to be able to see your raw (uncompressed) source code and be able to tinker with it to see what's going on. It doesn't help much to just see a link to a staging site because that code is compressed, super hard to read, and uneditable. If you'd like some help, we need access to that source. Ideally, a CodePen is best that isolates the issue. I see you provided a CodePen, but that's just our [working] demo, right? There are no issues with that CodePen you provided, right?