[Django] #36887: Unnecessary space introduced at top of changelist pages in 6.0

1 view
Skip to first unread message

Django

unread,
Jan 27, 2026, 12:42:17 PM (10 days ago) Jan 27
to django-...@googlegroups.com
#36887: Unnecessary space introduced at top of changelist pages in 6.0
-------------------------------------------+-----------------------------
Reporter: Jacob Walls | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: contrib.admin | Version: 6.0
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+-----------------------------
See [https://github.com/django/django/pull/19671#issuecomment-3714435724
report and screenshot], #36055 solved an overlap issue at the top of
changelist pages by splitting the header and action button into two rows,
when we could have just used flex layout to fix the overlap.

I have a patch ready along those lines.
--
Ticket URL: <https://code.djangoproject.com/ticket/36887>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 27, 2026, 12:44:22 PM (10 days ago) Jan 27
to django-...@googlegroups.com
#36887: Unnecessary space introduced at top of changelist pages in 6.0
---------------------------------+---------------------------------------
Reporter: Jacob Walls | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: contrib.admin | Version: 6.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
---------------------------------+---------------------------------------
Changes (by Natalia Bidart):

* stage: Unreviewed => Accepted
* ui_ux: 0 => 1

Comment:

Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/36887#comment:1>

Django

unread,
Jan 27, 2026, 1:25:06 PM (10 days ago) Jan 27
to django-...@googlegroups.com
#36887: Unnecessary space introduced at top of changelist pages in 6.0
---------------------------------+---------------------------------------
Reporter: Jacob Walls | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: contrib.admin | Version: 6.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
---------------------------------+---------------------------------------
Comment (by Jacob Walls):

Well, my intended fix just re-causes #36331. I'm not sure we should have
closed with #36331 with a revert; we could have just doc'd it. `django-
filer` (source of bug report) already coped with the change, see
[https://github.com/django-cms/django-filer/pull/1523 PR].

What is our backwards compatibility guarantee for extending admin template
blocks?
--
Ticket URL: <https://code.djangoproject.com/ticket/36887#comment:2>

Django

unread,
Jan 27, 2026, 1:34:53 PM (10 days ago) Jan 27
to django-...@googlegroups.com
#36887: Unnecessary space introduced at top of changelist pages in 6.0
-------------------------------+---------------------------------------
Reporter: Jacob Walls | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: contrib.admin | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------+---------------------------------------
Changes (by Jacob Walls):

* has_patch: 0 => 1
* needs_tests: 0 => 1
* severity: Release blocker => Normal

Comment:

Given that the best solution here involves a change to template
composition, I'm not convinced we should backport. I already have
something ready for discussion, so I'll post it anyway as a
[https://github.com/django/django/pull/20601 draft PR].

It's just a little whitespace; we can defer it to 6.1 and ensure more
testing occurs.
--
Ticket URL: <https://code.djangoproject.com/ticket/36887#comment:3>
Reply all
Reply to author
Forward
0 new messages