[GSDevTools + ScrollTrigger seem to create a bug]

3 minutes ago, GreenSock said:

That's a good suggestion. I just added a console.warn() message if you use an animation that has a ScrollTrigger applied. 

Awesome! You folks, and this forum format, are amazing!

 

4 minutes ago, GreenSock said:

I didn't quite understand what you mean. cdpn.io is already whitelisted. Can you provide a minimal demo that shows the problem you're running into so that we can troubleshoot? 

So I inspected DOM and opened the iframe URL in a new tab to this:

 

It seems like refreshing fixes this warning more than half the time, but it still pops up every now and then.

[GSDevTools + ScrollTrigger seem to create a bug]

Please add cdpn.io to PRO-whitelisted domains. I'm trying to refresh on the bottom part of the frame so I opened the iframe url and it's throwing.

[GSDevTools + ScrollTrigger seem to create a bug]

So ScrollTrigger is literally just that? If you hit y coord, it triggers some anim? Fine.

Not being facetious but some "ScrollTrigger and GSDevtools don't play nice together because ScrollTrigger auto-triggers an animation when you hit a specific Y-coord so there's really no way to scrub through it. 🤷‍♂️" console.error would save everyone some time in the future.

[GSDevTools + ScrollTrigger seem to create a bug]

When I scroll down, I expect the red block to activate an animation that slides it to the right when `.box` enters the viewport. This works as expected when GSDevtools is disabled.

 

When I add GSDevtools though, it doesn't trigger the animation when you scroll down.

 

For some reason it does trigger the animation (even with GSDevtools) if you are already scrolled down to the red block and refresh the page.

 

Definitely seems like a bug, but maybe there is some workaround setting so I can get back to studying ScrollTrigger. 🤞😅

See the Pen rNJLOgP?editors=1010 by corysimmons (@corysimmons) on CodePen