-
Let me share what we considered...
In all of the following
this
means the current page,n
means a numbered version ofthis
.*
asterix around something indicate where we might bold or highlight a page.Choices:
<< < this > >>
|< < this > >|
first prev this next last
{min} {-2} {-1} *{n}* {+1} {+2} {max}
first {-2} {-1} *{n}* {+1} {+2} last
first {-2} prev {n} next {+2} last
|< {-2} {-1} current {+1} {+2} >|
|< {-2} {-1} *{n}* {+1} {+2} >|
|< {-2} {-1} this {+1} {+2} >|
Page {X} of {Y} : First < {-1000} {-500} {-100} {-50} {-10} {-2} {-1} *{n}* {+1} {+2} {+10} {+50} {+100} {+500} {+1000} > Last
Page [{X}] of {Y} : First {-1} *{n}* {+1} Last
#10 is how vBulletin did it, and links are only shown if valid, navigation is removed altogether if page is 1 of 1. Our big complaint with this is the uselessness of so many options, that mostly they were used to binary search a long thread (and a page number entry box would've been a more powerful way of doing that), and finally that such huge navigation would never work on mobile.
#11 was what we decided on. It's compact and offers a really simple and intuitive pagination control. The “Page x of y” text places the “First... Last” in context. For most users advancing next, prev and first, last is all the navigation required. The {X} within “Page x of y” is a form control, hitting enter on that form will submit the form and launch a navigation jump to the designated page (if valid). If the number is above y, or below x, or not a number, then nothing will happen. This control gives power users the ability to jump around, binary searching the discussion.
Only valid links are displayed, and if there is only a single page, the pagination control is not shown at all.
Or if you want... you can just imagine we designed it like that for shits and giggles.
-
The {X} input for jumping pages - I'm looking at this on an iPad so I can't tell, but is it a
<input type="number" />
?
The min/max and spinner controls would make that a really handy little control. You could hide the spinner stuff until it was focused.Edit: just tested on the phone, no it's not. If it was the phone keyboard would be the numbers one, not the qwerty.
What's the logic in calculating the amount of pagination to show?
Seems a bit odd to have a 16 page thread like this and only seeing two buttons. It's also counterintuitive that the rightmost button is not necessarily the last page in the thread, but looks like it is. You see '1,2,last', so you click on 'last' expecting to see page 2, but end up on page 16. Maybe it just needs a gap as a visual clue.