-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs with gsap scrolltrigger in Safari #270
Comments
I've stumbled upon this issue in safari as well. And as you say, the scroll trigger seems to work fine on Chrome and Firefox. |
Experiencing a similar issue here – my GSAP ScrollTriggers are exhibiting unexpected behavior in Safari, whereas they function correctly in Chrome. Below is a snippet of the code:
|
I gave it another shot with: Seems like the new version of gsap and scrolltrigger has changed something but made it even worse. In general, lazyload still breaks the scroll trigger position --> it is not where it should be. That kind of worked (with a workaround) before with older versions of gsap/scrolltrigger: The workaround was to update the scrolltrigger frequently (every 2 sec was enough while scrolling in my case): That is by far not an elegant solution! Today I tried it with the latest versions of gsap/scrolltrigger. Not changing anything, the scrolling of the whole website was completely buggy and glitchy. Feels like every scroll movement the website jumps 100px up and 100px down. I then removed: --> Scrolling was again how it is supposed to be, but still the same issue of wrong scrolltrigger trigger position came back. Now I again gave up and switched back to the old gsap versions (3.9.1). Any ideas? |
I experience bugs when used together with gsap scrolltrigger. Page works without problems without lazyload with scrolltriggers but when adding lazyload things start to be different. Lazyload somehow breaks the scrolltriggers and I have to refresh them in order to make it work again. Scrolltriggers start to be at wrong places when using lazyload.
Tested in Safari. Chrome and Firefox seem to have less issues.
Is this a known issue?
The text was updated successfully, but these errors were encountered: