-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
PaletteEdit: Add appropriate size props to Buttons #66590
Conversation
@@ -215,6 +215,7 @@ function Option< T extends PaletteElement >( { | |||
<Item ref={ setPopoverAnchor } size="small"> | |||
<HStack justify="flex-start"> | |||
<Button | |||
size="small" |
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.
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.
This predates my involvement so I can't comment with confidence on the intentionality. Aiming for 40px
rows seems acceptable to me though.
This whole UI likely needs to be revisited and standardised at some point.
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.
Ok, let's leave it like this for now until we have time to revisit.
__next40pxDefaultSize | ||
className="components-palette-edit__menu-button" |
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.
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.
Classname addition makes sense to resolve this.
I just wonder if these buttons make sense to be menu items instead of buttons?
Not something to block the PR of course.
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.
Right, it looks like this could be a DropdownMenu.
@ciampo Should we add any new dropdown instances using DropdownMenuV2, or should we still use v1 until it's a bit more stable?
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
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.
Looking good, given that we agree on the palette edit item size 👍
__next40pxDefaultSize | ||
className="components-palette-edit__menu-button" |
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.
Classname addition makes sense to resolve this.
I just wonder if these buttons make sense to be menu items instead of buttons?
Not something to block the PR of course.
Flaky tests detected in 0661a62. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11596713065
|
* PaletteEdit: Add appropriate size props to Buttons * Add changelog Co-authored-by: mirka <[email protected]> Co-authored-by: jameskoster <[email protected]> Co-authored-by: tyxla <[email protected]>
In preparation for #65751
What?
Adds appropriate size props to the remaining Buttons in PaletteEdit.
Testing Instructions
See the PaletteEdit story in Storybook.