-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Try: Remove menu item min-width. #25218
Conversation
Size Change: +63 B (0%) Total Size: 1.21 MB
ℹ️ View Unchanged
|
@jasmussen Woo! Thanks for this one ❤️ I just tested it locally. I've noticed some issues with some of the Toolbar dropdowns (for the Cover block): This could perhaps be resolved by adding This leads to another issue, at least if the dropdown happens to have overflow 🙈 : I gave that a shot. It worked (at establishing a better min-width). The other issue is that the icon is really close to the text (almost touching). This echos an issue with the Button/MenuItem icon setup, rather than min-width. With all of that being said!! (Phew). (Not really sure how deep the rabbit hole goes on this one, but maybe worth taking a look?). Ultimately though, I agree with your original mission in that, I too believe Dropdown menu widths should be more adaptive/flexible. |
e0a0e50
to
418e223
Compare
@jasmussen 🎉 ! Looks like it's working :). |
🙈
When I try to run
(I tried blowing away Docker's resources and starting from scratch. It didn't seem to help) Don't let me be a blocker for this one! If anyone else can help with E2E tests, by all means ❤️ |
Thanks so much for looking and fixing! I'll have another stab, and otherwise we'll find a way. |
41b585d
to
070374d
Compare
I pushed a few tweaks and rebased/squashed. Let's see if it does anything. |
I could use help with this one. @gziolo would you have any insights and/or time? |
It looks like some e2e tests that use XPath need to be updated to reflect changes in HTML syntax. |
e59f14c
to
a0f3a3a
Compare
e609bf5
to
8d7810a
Compare
package-lock.json
Outdated
@@ -46068,7 +46068,7 @@ | |||
"dependencies": { | |||
"clone-deep": { | |||
"version": "0.2.4", | |||
"resolved": "https://registry.npmjs.org/clone-deep/-/clone-deep-0.2.4.tgz", | |||
"resolved": "http://registry.npmjs.org/clone-deep/-/clone-deep-0.2.4.tgz", |
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.
I guess it shouldn't be in this PR. We can clean it up later...
8d7810a
to
a636e57
Compare
I see similar e2e test failures in the |
Since this PR is not urgent, I'll let it sit until the failures in the master branch are taken care of, then I'll rebase and we can review again. Thanks so much for all the help @gziolo ! |
bc3bfac
to
303f222
Compare
303f222
to
6c77439
Compare
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.
Tests are now passing and works as described. 👍
I noticed the properly sized drop down after applying the patch and did not find any regressions.
Awesome, let's try this, and I'll follow up and re-apply min-widths in specific cases if they turn out to be necessary! |
Popovers have a min-width. Which means you get very wide popovers in some cases:
This PR tries removing that, so they look just right (sized according to the content inside):
So why was it added in the first place? Well, it was added back in #9086 because an auto-expanding URL field didn't resize it. With this PR I'm revisiting that, though, because: should a textfield ever expand a popover? Isn't it best those have fixed sizes? And currently, they do:
So, this PR would be a nice little win for toolbar dropdowns, and even a bit of cleanup. But it'd be good to test existing popovers to make sure they work as intended.