Literally 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.<p>Opera seemed like the only browser vendor that truly championed next/prev.<p>I only do it now as a habit because of Opera - and, since switching to Chrome after Opera's nadir, for accessibility, regardless of whether screenreaders respect it. But I probably wouldn't know about it if not for Opera.<p>It's both wistful and aspirational to use them, because this is the way browsers were supposed to work - as was generally the case with most things Opera, of course.
I wonder why they recommend putting <link rel="..."> tags into the head, instead of marking up existing <a href> tags (which you'll have in most cases for prev/next) with rel-attributes. Actual difference in parsing? Just because <a> tags might not be on <i>every</i> site?
One of their examples is a single sentence split over three pages of an article. I'm not sure if that's just a toy example, or also a jab at the way clickbaiters game the view counts.
Ah, this might be the cause of the infuriating behavior where you search for a term, and it appears in one page in a huge forum thread, but after clicking on a search result you end up somewhere completely else in the thread.<p>I don't know whether Google sends you there, or whether the site redirects you from the "view all" page to the first page, but the result is pretty annoying.
Besides making the big G happy, these semantic relationships also helps libraries authors to easily traverse a series purely on the front end. Years ago, I looked at Github's pagination API [1] and discovered this approach also makes infinite paging much easier, just send me a bunch of next pointers until there aren't any more. So I decided to support this format by default.<p>[1]: <a href="https://developer.github.com/guides/traversing-with-pagination/" rel="nofollow">https://developer.github.com/guides/traversing-with-paginati...</a><p>[2]: <a href="https://github.com/backbone-paginator/backbone.paginator" rel="nofollow">https://github.com/backbone-paginator/backbone.paginator</a>
How do you guys implement / What's the best practice for paginating your db using sql and nosql?<p>I know there are a bunch of gotcha's to look out for
One of the nice things this does is give the browser's "reader mode" a hint where the next page is. And it's great. Only problem is, publishers seem to have no interest in helping the reader mode. On the contrary, many seem hell-bent on defeating its content detection algorithm, etc, to make it useless so we all look at their stupid ads.