Jump to content


ScrollTo bug in 1.8.2 in Safari 6.0.2 & Mountain Lion

Warning: Please note

This thread was started before GSAP 3 was released. Some information, especially the syntax, may be out of date for GSAP 3. Please see the GSAP 3 migration guide and release notes for more information about how to update the code to GSAP 3's syntax. 

Recommended Posts

double triggers in some cases. Correct me if i'm wrong.


It doesn't double trigger, it works smoothly, it's the best solution I found. With scrollTo plugin I had the same issues with Safari, even with autoKill, only jQuery scrollTop seemed to work seamlessly across all devices and browsers.

See my earlier posts in this thread for more details about the issue I faced. Low FPS also causes scrollTo to diе.


Anyway, tweak and see what you get, but I can't suggest waste time trying to get scrollTo to work on properly.

Link to comment
Share on other sites

Hi again and thank you for the reply, and you are right about your suggestion.  ;)

By the way, I was trying to remember where I came accross the double triggering issue, it was on Firefox. You can cheeck it here:


Open firefox console and you should be faced with two logs from the same callback.
It probably doesn't break your code but you can end up with performance issues if you're relying heavily on this callback.

Link to comment
Share on other sites

Having trouble understanding what bug you are talking about.


Can you please provide a very simple demo that clearly illustrates the issue and provide detailed instructions.


We would love to resolve any issues, but it would really help to be sure we are seeing what you are seeing.



Link to comment
Share on other sites

Hi Carl,
first off, Merry Christmas to all.

I made some test cases to try and reproduce this in a simple example, and at first I wasn't able to, which was making me believe it had something to do with my code, and than I opened the developer tools on safari and started recording to see the FPS, it just started breaking the scrollTo animations. This makes me believe that it's really an FPS issue. On my main page it happens without opening the dev tools and recording, but there are a lot of animations going on, which at some points may bring down FPS.


Here is the test url:

Unfortunatly I can't post here the real page i'm developing because of corporate secrecy. Thank you for your understanding and time.

Link to comment
Share on other sites

Hi Rui,


Thanks for the demo and more info. I appreciate the simplicity of the test. In the future it will make it easier for us to test if you provide a zip of your file(s) too. 

As you noted, enabling the timeline recording in Safari did trigger the interrupted tweens. Please try enabling autoKill:false as that seems to make things run fine.

TweenMax.to(window,speed,{scrollTo:{y:targetPos}, autoKill:false});
  • Like 1
Link to comment
Share on other sites

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.