What are the recommendations for infinite scroll?
Don't use it. It's an antipattern and an awful meme.
Why's that?
Pagination with rel=“next” and rel=“prev” (2011)
11–20 of 96 posts
Re: Pagination with rel=“next” and rel=“prev” (2011)
#12Also known as a good way to break many a SPA.
Re: Pagination with rel=“next” and rel=“prev” (2011)
#13Earlier quoted context omitted.
Don't use it. It's an antipattern and an awful meme.
Why's that?
Pages become so complex that browsers start lagging. If you click a link on the infinitely scrolling page and then come back, your position is lost and you have to scroll down the whole way again (see Facebook, Twitter).
Re: Pagination with rel=“next” and rel=“prev” (2011)
#14Earlier quoted context omitted.
Don't use it. It's an antipattern and an awful meme.
Why's that?
It is extremely rare that it doesn't bring my browser to its knees after a certain amount of scrolling. (This is with 12 GB on Chrome.)
You will also end up losing your reading position after a browser restart or on iOS where Mobile Safari reloads a page to save memory.
It's a dumb, pointless feature that at the very least shouldn't be the default option. I'm sure there are hypothetical scenarios that may or may not warrant it, but it is a pain and a half for the user. Tumblr blogs have it in spades, and it's a miserable experience to browse.
Re: Pagination with rel=“next” and rel=“prev” (2011)
#15Re: Pagination with rel=“next” and rel=“prev” (2011)
#16Earlier quoted context omitted.
Don't use it. It's an antipattern and an awful meme.
Why's that?
OTOH:
- usually breaks the back button (e.g. scroll to the 20th page, click something, go back. welcome to page 1!)
- usually breaks links (how do you show someone things-on-page-10?) (fixable by tweaking the URL as you go, but nothing is really consistent + predictable by non-technical users)
- usually performs hideously on low-power machines (e.g. mobile) due to memory growth (there are techniques, but few use them). can even tank powerful machines in time.
- footers. headers. etc.
Re: Pagination with rel=“next” and rel=“prev” (2011)
#17What are the recommendations for infinite scroll?
Can anybody point to an implementation of infinite scroll that actually works? I know facebook's implementation doesn't work correctly because the scrollbar breaks when scrolling down using it.
Re: Pagination with rel=“next” and rel=“prev” (2011)
#18Re: Pagination with rel=“next” and rel=“prev” (2011)
#19How do you guys implement / What's the best practice for paginating your db using sql and nosql?
I know there are a bunch of gotcha's to look out for
Re: Pagination with rel=“next” and rel=“prev” (2011)
#20Literally one of the greatest things about the Opera browser was that you could browse an entire forum or whatever (longform article etc) with the Space key, because the browser would automatically go to the `next` page on hitting the bottom of the page. They also did some cool stuff with swiping to the next page on mobile. Opera seemed like the only browser vendor that truly championed next/prev. I only do it now as…
I saw recently that Safari's reader view actually pieces together paginated articles into one long view. I haven't had a chance to try it myself though.