New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed 34039 - added min-width to the admin searchbar on small devices. #16091
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello! Thank you for your contribution 💪
As it's your first contribution be sure to check out the patch review checklist.
If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket!
If you have any design or process questions then you can ask in the Django forum.
Welcome aboard ⛵️!
@clytaemnestra Thanks for this patch 👍 As far as I'm aware, we should stretch the entire block not only the search bar to get: instead of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🌈 tested in Firefox 104, Chrome 92, Ubuntu 20.04 – and Safari 15.6.1 macOS 12.5.1
@felixxm we ended up only fixing the width of the input, not whether or not the whole toolbar (and its background) spans the whole of the screen or not. This whole flexbox implementation is a bit harder to work on.
If we want to fix the toolbar’s background taking up the whole width – could we make that as a separate ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I just realised we have more work to do on the tests 🤦
Tests are fixed. @felixxm I created another ticket for that issue: https://code.djangoproject.com/ticket/34047, as agreed above. I could pick it up and check it out, once it's approved. |
@thibaudcolas Due to the fact that fixing #16091 is complicated with the current HTML structure, maybe it would be better to close ticket-34047 as a duplicate and fixed both issues together. What do you think? |
Closing due to inactivity. |
Fix for: https://code.djangoproject.com/ticket/34039.