Jump to content
Search Community

Header Jump Issue on Different Screens

Ziafat Ali
Moderator Tag

Recommended Posts

GSAP Helper
Posted

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. 

  • Thanks 1
Ziafat Ali
Posted

My Apologies,

 

This is the example but it's working well here and not in my project

 

See the Pen VwJzydb by ryan_labar (@ryan_labar) on CodePen.

 

Thanks!

Posted

Hi,

 

If it's working on the codepen and not in the site, that means something else in your setup is interfering with the way the code should work.

 

Make sure that the ScrollTrigger instances are created in order. If you are using a theme, be sure to remove any CSS transition from any element that is animated with GSAP.

 

Also is worth noticing that the extension in pixels of your ScrollTrigger is just 41 pixels, in some OS/browsers the amount in pixels of a wheel event can be of 100 pixels and depending on hardware and OS configuration it could be more or less, so that means that in a single wheel event the ScrollTrigger start and end points will be passed.

 

I think the best approach is to handle everything in a single Timeline and give that part some extra scrolling.

 

Hopefully this helps

Happy Tweening!

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...