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.
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.
