Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#32903 closed Bug (invalid)

admin page in Google-Chrome does not show the columns like in Firefox or Chrome

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

Description

using Google Chrome 91.0.4472.114 (Official Build) (64-bit) the admin page (/admin/polls/question/) from Tutorial looks very strange as the left column is not visible. (In other projects with filter the filters on the right side are also not visible).

  • Firefox (89.0.2 (64-bit)) looks good
  • Chromium (Version 91.0.4472.114 (Official Build) snap (64-bit)) looks good
  • I using Ubuntu 18.04.

Attachments (2)

django32_poll-tutorial_Google-Chrome__2021-07-05_NOK.png (41.6 KB ) - added by elnikej 3 years ago.
Google-Chrome not visible menu in left side
django32_poll-tutorial_firefox__2021-07-05_OK.png (39.5 KB ) - added by elnikej 3 years ago.
Firefox menu in left side is visible

Download all attachments as: .zip

Change History (5)

comment:1 by Tim Graham, 3 years ago

It seems doubtful that Django is at fault but could you attach a screenshot that demonstrates the issue? I took a quick look and don't see a difference between Firefox and Chrome.

by elnikej, 3 years ago

Google-Chrome not visible menu in left side

by elnikej, 3 years ago

Firefox menu in left side is visible

comment:2 by Mariusz Felisiak, 3 years ago

Resolution: invalid
Status: newclosed

Thanks for the screenshots, however I cannot reproduce this issue. It looks like a problem with refreshing CSS files, I don't think that Django is at fault. Can you try to use CTRL+F5?

comment:3 by elnikej, 3 years ago

I did some more tests with CTRL+F5 and loading different project.

  • in Django3.2 after refresh it looks good in all Browsers
  • if I open a Django2.2.24 admin page and after that Django3.2 admin page I have the same situation again
  • You are right some css is in Browser Cache

Thanks for sorting that out.

BR Jens

Note: See TracTickets for help on using tickets.
Back to Top