WordPress.org

Make WordPress Core

Opened 3 years ago

Last modified 7 months ago

#37228 new enhancement

Consider to rethink and improve the list tables pagination links

Reported by: afercia Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-screenshots needs-patch
Focuses: ui Cc:
PR Number:

Description

Splitting this out from #33962. See also #32558.

Quickly discussed at WCEU 2016 Vienna's Contributor Day with @karmatosed and @hugobaeta and noticed the pagination links offer room for design improvements. Looks like there are no apparent reasons (other than historical ones) why the top and bottom pagination links should differ and maybe the editable input field should be displayed only when there are more than 3 pages.

As @helen pointed out, also the interactions could benefit from some rethink.

This would probably be a very nice ticket for designers willing to contribute :)

Current state on 4.6 trunk:

https://cldup.com/jPRxp_462C.png

with longer translated strings:

https://cldup.com/lkdtPkEn0P.png

Change History (3)

#1 follow-up: @hugobaeta
3 years ago

Like you said and shown with the screenshots, there are currently two UI patterns for table navigation:

  • the one at the top the table, uses an input field for the current page number, so one can navigate quickly to others - let's call this the "input navigation"
  • the one at the bottom of the table, just lists the page number and context ("1 of X") - let's call this the "simple navigation"

I had proposed in our conversation we switch both to a consistent pattern on top and bottom, one based on context: if there are less than 3 pages, show the "simple navigation" (no input, since the user can navigate all the pages, up to 3, with the first/previous/next/last buttons); if there are more than 3 pages, then we use the "input navigation", as it will help the user get to any page more quickly.

Thoughts?

#2 in reply to: ↑ 1 @melchoyce
3 years ago

Replying to hugobaeta:

I had proposed in our conversation we switch both to a consistent pattern on top and bottom, one based on context: if there are less than 3 pages, show the "simple navigation" (no input, since the user can navigate all the pages, up to 3, with the first/previous/next/last buttons); if there are more than 3 pages, then we use the "input navigation", as it will help the user get to any page more quickly.

Thoughts?

This sounds good to me.

#3 @desrosj
7 months ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to Future Release
Note: See TracTickets for help on using tickets.