Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#33094 closed Cleanup/optimization (wontfix)

"Show all" is ambiguous

Reported by: Richard Laager Owned by: nobody
Component: contrib.admin Version: 3.2
Severity: Normal Keywords:
Cc: Carlton Gibson Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The admin interface used "Show all" with two different meanings. One is to disable pagination (a query string of ?all=). The other is to disable filters (a query string of ?), when show_full_result_count is False.

I propose changing the latter to "Clear search" and have submitted a PR here:
https://github.com/django/django/pull/14844

Attachments (1)

Screenshot_20210909_065351.png (18.0 KB ) - added by Mariusz Felisiak 3 years ago.

Download all attachments as: .zip

Change History (4)

by Mariusz Felisiak, 3 years ago

comment:1 by Mariusz Felisiak, 3 years ago

Cc: Carlton Gibson added
Resolution: wontfix
Status: newclosed
Type: BugCleanup/optimization

IMO, "Show all" is more accurate, because it also clears filters, not only "Search". Also, "Show all" links appear in different places which makes them sufficiently distinguishable:


It's also documented.

comment:2 by Richard Laager, 3 years ago

Has patch: set

comment:3 by Richard Laager, 3 years ago

Fair enough. I didn't realize it cleared filters too. (Edit: I obviously should have realized this, since I noted the query string was empty.)

Part of my motivation here is that I'm upgrading from an old version of Django. It showed the pagination at the top of the page too, so there was a "Show all" link near the top of the page previously, and there is now, but they have different behaviors. I didn't expect this argument to carry much weight at this point, though, as people should be through this change already if they're staying on supported versions.

I closed the associated PR.

Last edited 3 years ago by Richard Laager (previous) (diff)
Note: See TracTickets for help on using tickets.
Back to Top