Can I just say that, while the scrolling worked without issue for me, it was useless and annoying, and the number of problems other people are having with it made me wonder why you'd go to the trouble. As respectfully as I can say it, this is the very definition of dancing baloney. You had to put effort into this dorky effect that is arguably worse than a plain scrollbar, and to add insult to injury, now you're having to take bug reports because one of the oldest, most fundamental features of a web page (scrolling to see more) is complicated to the point that it doesn't work cross-browser.
Please just let the scrollbars work the way they're supposed to.
Yeah the scroll didn't come out as well as well as I had hoped. I went trough the trouble because I like experimenting with user interactions. I saw what Apple did with the locked scroll for their new iPhone promotions and wanted to do something like that but less restrictive.
Initially i had a implementation that didn't lock you in but tried to predict where you where going and adjusted scroll speed accordingly. While it worked pretty well the behaviour was so strange that you needed some primer before using it. So I settled on just locking you in since the design is very focused on this effect. We might redo the site with slightly different graphics and a "normal" scroll later.
So there you have it, the story of the useless, buggy, dorky dancing baloney scroll. :-)
(And yes, I spend way too much time on stuff like this)
Possibly related?: scroll down, then up. Before it reaches the top position, it locks up Firefox Aurora (current nightly build). Possibly a bug in Firefox, but those are relatively rare, even in the nightlies.
Seems window.scrollTo does not work properly in safari when you kick the layers in to hardware accelerated mode.
I've disabled the snapscrolling now on all Safari versions. Try it now! I think I'll end up disabling it everywhere since people seem not to like it that much :)
