#33095: Admin actions shown with zero results
-------------------------------------+-------------------------------------
Reporter: Richard Laager | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.admin | Version: 3.2
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Richard Laager):
* has_patch: 0 => 1
Comment:
Replying to [comment:2 Mariusz Felisiak]:
> Yes I believe that's intentional. It's true that you cannot do anything
when there are no results on the page, however you can change filters
dynamically and toggling actions every time would make it annoying.
"wontfix" as for me, but I'm not a UX expert, so let's wait for the second
opinion.
Fair enough, but let me ask a couple follow-ups then... Is this important
enough to justify a SELECT COUNT(*), which there are a bunch of complaints
about in #8408? But more to the point, if this is going to show the
actions if there are ''any rows in the table'', then why not just
''always'' show the actions? Surely it's not common to have a database
table with 0 rows. And the same argument about the UI changing applies
there too... it's going to change as soon as you add the first object.
--
Ticket URL: <https://code.djangoproject.com/ticket/33095#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.eb472f5eff2bc1a3989c4f7ccaef0445%40djangoproject.com.
