#35747: Admin change list doesn't redirect to default ordering when the last
ordering field is removed from sorting
-------------------------------------+-------------------------------------
Reporter: ldeluigi | Owner: (none)
Type: Bug | Status: closed
Component: contrib.admin | Version: 5.1
Severity: Normal | Resolution: invalid
Keywords: admin change list | Triage Stage:
ordering sorting sortremove | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => invalid
* status: new => closed
Comment:
> For example, if the query parameter is the default o, the redirect
points to /?o=, which results in the change list not being ordered at all.
To me, the change list is ordered with the default ordering. The columns
"appear" to have no ordering applied which might cause confusion. But I
also think the suggested change makes the UI confusing as you are not able
to "remove" the ordering in the UI when you have it ordered by one column,
click to toggle it off, and the page reloads without any changes to the
UI.
I don't think there is a clear bug here, and currently prefer the way it
is.
Your PR would need a test which might help clarify the expected behavior
--
Ticket URL: <https://code.djangoproject.com/ticket/35747#comment:2>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191d6a12f00-0335c431-78e1-48cd-adb4-4340398387d5-000000%40eu-central-1.amazonses.com.
