[richo]

Scroll from the top to the bottom (or vice versa) really hard.

Watch the "3d layout engine" flip out thoroughly (tested only on chrome stable on darwin)

[squeaky-clean]

Try grabbing the scroll bar with your mouse and pulling it down the page. Nope, apparently scrollbars aren't for that.

This doesn't seem to be designed with regular desktop usage in mind.

[dagurp]

I don't know why but it seems to be perfectly acceptable to break the scrollbar these days.

[madeofpalk]

I don't think it is. Famous is the first I've seen to complement reimplement (and fuck up) something as fundamental as scrolling.

[dagurp]

What about the countless sites that have infinite scrolling (Facebook for example)? It's not as bad as Famous but still breaks it in my opinion.

[madeofpalk]

Infinite scrolling doesnt break scrolling, it breaks backwards/forwards navigation.

[dagurp]

It does both (infinite scrolling is a horrible idea). If you try dragging the scrollbar it will jump around every time more content is loaded and you lose your position on the page.

[brbcoding]

With that bounce-back effect it doesn't seem like it was designed with usage in mind.

[mkoryak]

I think it might be one of those "features" that someone thought would make the site look cool, but really just pissed off the users.

[larrybolt]

Apart from the slow pace at which the page scrolls back, the fact when it's doing so you cannot scroll up anymore (or down when you're at the bottom of the page) annoys me even more.

What Apple did, making scrolling behave like a sheet of paper confirmed using a rubber band, seems more natural than what this "3d layout engine" is doing. Giving it even more thought, it makes sense that even on a non-scrollable page scrolling (giving some form of input) should at least cause a confirmation that it recognised the action you preformed.

[mercer]

I also noticed that on my phone (Nexus 4) sometimes the scrolling just keeps going. I'm not sure that's how they meant it to behave, but even if it is, it's not great.