ScrollTrigger - Initial AUTO SCROLL - Strategy question

[newguy123]

Hi Everyone

 

If I want my Scrolltrigger, to 1st auto scroll a bit, could I simply add in a label at the point I want it to autoscroll to, and then simply add some code like this:

 

gsap.to(window, {
	scrollTo: tl.scrollTrigger.labelToScroll("mylabel"),
    duration: 1,
});

... and I dont need a click or interaction for that to work correct, and it will simply run and scroll to that label as soon as the page loads?

 

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

[newguy123]

Thanks Helper

 

To answer my own question then, yes seems my thought strategy works perfectly fine in this simple pen. Is there any reason NOT to do it like that, or simply, if it works, it works!?

See the Pen VwROdVN by newguy123 (@newguy123) on CodePen

[Cassie]

If it works it works really!

 

The only reason I can think of is that it's usually bad UX to hijack the scroll away from the user, you're effectively stopping the user from scrolling manually while that tween plays. But if that's not really an issue for you, then crack on!