#31576 closed Bug (fixed)
Navigation sidebar hides some elements on small windows.
Reported by: | Mariusz Felisiak | Owned by: | Mariusz Felisiak |
---|---|---|---|
Component: | contrib.admin | Version: | 3.1 |
Severity: | Release blocker | Keywords: | |
Cc: | Tom Carrick | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Navigation sidebar hides some elements, e.g. time/calendar pickers or filter horizontal widgets. It's a bug in a new feature, see #31034.
Attachments (2)
Change History (10)
by , 5 years ago
Attachment: | Screenshot_20200513_100151.png added |
---|
by , 5 years ago
Attachment: | Screenshot_20200513_095732.png added |
---|
comment:1 by , 5 years ago
comment:2 by , 5 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Owner: | removed |
Status: | assigned → new |
comment:3 by , 5 years ago
I'm not sure that we need go as far as removing the sidebar for mid-sized screens. Shutting the sidebar is sufficient to resolve the issue, and it's a nice improvement.
Similar discussion on the PR: Tom, Mariusz. That was to do with inline scrolling but with the same conclusion, "...it can be mitigated by just closing it, so I think it's alright from the user's perspective".
The error here only shows up on the selenium headless tests. Actually using the admin on a 800px viewport is fine, great even: you just close the sidebar if you don't want it.
I'm a bit reticent to loose it for the tablet sized screen for what seems like a testing artifact. (We could either set a wider viewport in the test, or ensure the sidebar is closed on a smaller screen, to be more realistic.)
comment:4 by , 5 years ago
Triage Stage: | Unreviewed → Accepted |
---|
Going to accept though, as we either have to fix the test or disable the feature.
comment:5 by , 5 years ago
Couple of things:
This probably isn't the right fix, but it should be possible to fix these tests by clicking the toggle after each request - actually after the first request, since it'll persist. I'm not actually sure of the persisting behaviour between tests, it might even be possible to close it once it in setUp()
This affects more the tests than actual users, however (IMO).
I do plan on looking at all the various display issues on the currently supported media queries between now and the non-blocking bug freeze, but I won't assign this particular ticket to myself yet in case anyone has more time before I get a chance to do that.
Proposed solution: