call007 Posted January 8, 2023 Share Posted January 8, 2023 Hi everyone, I've noticed this problem in 3.11.4 version of GSAP. When scrolling a page for the first time you can see the strange jumping of the content (around 15px). You can check it on the demo. Is there a way to fix it? Thanks See the Pen eYjzORQ by call007 (@call007) on CodePen Link to comment Share on other sites More sharing options...
Solution GreenSock Posted January 9, 2023 Solution Share Posted January 9, 2023 Thanks for reporting that, @call007! It should be resolved in the next release which I dropped into this fork: See the Pen rNrjqWy?editors=1010 by GreenSock (@GreenSock) on CodePen  In the meantime, though, you can just add this one line of code to fix 3.11.4: smoother.scrollTrigger.getTween().resetTo("totalProgress", 0); (Obviously that entails saving your ScrollSmoother as a variable named "smoother")  Better?  Sorry about any confusion there! 3 Link to comment Share on other sites More sharing options...
call007 Posted January 9, 2023 Author Share Posted January 9, 2023 It works fine with this line (and in the demo above) : smoother.scrollTrigger.getTween().resetTo("totalProgress", 0); Â Thank you for your help! Good luck! 2 Link to comment Share on other sites More sharing options...
call007 Posted March 27, 2023 Author Share Posted March 27, 2023 @GreenSock Unfortunately, this problem wasn't fixed with the new version (3.11.5) of GSAP 😬 Link to comment Share on other sites More sharing options...
Cassie Posted March 27, 2023 Share Posted March 27, 2023 Â On 1/9/2023 at 7:52 AM, call007 said: It works fine with this line (and in the demo above) : Could you just verify again that it works in the demo above? If so I wonder if there's some caching going on with your local setup or some other issue in the code? Link to comment Share on other sites More sharing options...
call007 Posted March 27, 2023 Author Share Posted March 27, 2023 12 minutes ago, Cassie said:  Could you just verify again that it works in the demo above? If so I wonder if there's some caching going on with your local setup or some other issue in the code? No, it's not working properly. The forked demo above still has the same problem. But I remember it worked fine in the demo above a couple of months ago😕 Link to comment Share on other sites More sharing options...
GreenSock Posted March 27, 2023 Share Posted March 27, 2023 Sorry about that, @call007. An improvement we made in another area of the codebase before releasing 3.11.5 caused that regression but it should be resolved in the next release. I dropped the beta into the demo and it does seem to resolve things, right?:Â See the Pen rNrjqWy by GreenSock (@GreenSock) on CodePen 3 Link to comment Share on other sites More sharing options...
call007 Posted March 28, 2023 Author Share Posted March 28, 2023 @GreenSock , it's ok, thanks! Your demo works properly now. Hopefully, it will be fixed in the next release. Thanks 🙂 1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now