ng-bootstrap / ng-bootstrap

Angular powered Bootstrap
https://ng-bootstrap.github.io
MIT License
8.22k stars 1.55k forks source link

Pagination: replace icons with text (suggestion) #1427

Closed thbt closed 7 years ago

thbt commented 7 years ago

This is just a suggestion : replacing the pagination's boundary and direction links icons with text (First/Last and Previous/Next) could improve the UX design of this library. The idea is to clearly separate them from the page numbers. Another thing to consider is to drop the First and Last links, as they are already present when using ellipses.

Here is a few blog post about pagination best practices for UX design :

pkozlowski-opensource commented 7 years ago

I'm reading through the linked articles (which seem like a copy of one another, btw) but based on my understanding those articles do not advocate usage of text in place of symbols. Here are the relevant sections, IMO:

In most cases, Previous and Next links are very useful for users. But, in order to create a decent pagination control, you should clearly separate them from the page numbers and give them sufficient distance or unique styling so that they can't be mistaken as a page; this is particularly pertinent if you use arrows instead of text for Previous and Next.

What is really says is that prev / next controls shell be visually distinctive, but not necessarily textual! I kind of agree with this but:

Then the next relevant section would be:

Some paginations have first and last links that allow users to skip to the first or last page. This is unnecessary and ususally confuses users. Sometimes the first and last links are displayed using double arrowheads, which users will often mistakenly click thinking it’s the single arrowhead link that takes them to the next page. Labeling the links “first” and “last” also causes clicking errors because of its proximity to the “next” and “previous” link.

This section just says not to use first / last at all and clearly states that using text instead of symbols doesn't help at all. Once again, I don't think we are concerned since users can opt-out of those controls.

The final argument against changing defaults is that users can already change symbols to any text they like by translating templates. If anything, we should think of ways of providing custom templates for page cells (this is a long-term goal, not something to look into now).

Closing given all the above.