[ScrollTrigger - The pin spacer element add a padding bottom on the end of my scroll if i've two same components.]

Hi @Cassie
Yes i can assume that's really difficult to figure out without the demo,
here i've made a quick record of the issue:

And the weird things is that don't make it every time... If i've an hot reload on my page, all is fine...

[ScrollTrigger - The pin spacer element add a padding bottom on the end of my scroll if i've two same components.]

Hi!

 

I tried, without result, to reproduce a bug that I encounter in my application:
When two identical components running the same animation for its content follow each other and I scroll to the end of the second component, the "pin spacer" is updated and adds a padding bottom the size of the scroller, which gives the impression that it "jumps" above the viewport.

In the code pen, I tried to reproduce the same structure, but without the same effect. Does anyone have any idea what could cause this?

 

I know, it's not easy without a demo of the bug... But i swear i've tried, and because i don't exactly know what can cause it... I'm not able to make a correct minimal demo for isolate my issue... Any supports will be great!

Thanks in advance

See the Pen BarvQpo by charlene-bx (@charlene-bx) on CodePen

[Scroll Trigger does not seem to work on elements with hidden overflow]

Hello everyone!
I've been trying to create a kind of paralax for a while but I'm still stuck on one thing: I can't trigger the scroll triger when the container has its overflow hidden: why?

Quick little demo attached,

thanks for any help

See the Pen dymbKWj by charlene-bx (@charlene-bx) on CodePen

[Best practices for GSAP and Nuxt?]

Hello everyone,
I was also wondering: after having done several tests, I arrived at a decomposed architecture with VueJS:

 

I initialize my tweens and subtimelines in the computed properties and mount the final timeLine to the mounted hook.

I've made a rapid and ugly sample on CodePen for those who are interested:

See the Pen ExQONzE by charlene-bx (@charlene-bx) on CodePen

 

But being also a big console.logger, I recalled that the computed are all initialized at the creation of the component... So in a way, they are launched the first time (but the animations doesn't run... And i don't understand very well why btw). But is this really a problem? The animations are only launched once they are aligned on the timeline, so in the mounted... If anyone has any suggestions for improvements, or any other suggestions, I'd love to hear about them!