[digitaltoad]

Doesn't this still effectively break the back button or at least the users view of the back button? To the user although there are visual hints, he/she hasn't left the page. Scrolling down the page however creates multiple history entries.

[timmclean]

Nope, this seems to use history.replaceState, not pushState: https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/M...

[DangerousPie]

I don't think it does, at least not on Firefox. When you scroll down the URL just updates without a history entry being added.

[iambateman]

It does.

This would be perfect if clicking the nav didn't cause a page reload. I expect the page to go back to an entirely previous page, if I hit the back button in this case.

That would not be the case if the sections of content were different from one another.

- A super-scrolling page with different sections of content might keep the back button functionality the way it is here.

- Homogeneous content like Facebook posts should not incur a back button through the pagination.

IMHO. But this is super cool otherwise.

[digitaltoad]

I was mistaken. I must have clicked through to a page.