Global Styles: Move the 'Edit colors' button to a standard menu item#36842
Global Styles: Move the 'Edit colors' button to a standard menu item#36842noisysocks merged 3 commits intotrunkfrom
Conversation
|
Size Change: +30 B (0%) Total Size: 1.11 MB
ℹ️ View Unchanged
|
|
The styling of the disabled menu is not quite right, but will fix that tomorrow if there is agreement to go ahead with this interim fix |
|
Thanks for working on this fix, @glendaviesnz!
Agree, and there's also something weird with the width of the items: Also, if you open the menu and there are no colors, the option to remove them is enabled. However, it's a bit weird to open a menu and find that none of the options can be clicked, so I wondered if we could disable the ellipsis in that initial state. |
86788d7 to
5b7c67b
Compare
|
@javierarce there isn't currently a disable prop on that dropdown component, but just removing the menu when not needed seems to provide a reasonably smooth experience: What do you think about that approach? Have pushed this to the PR if you want to test it. |
7a65672 to
28f1581
Compare
| onClose(); | ||
| } } | ||
| className="edit-palette-menu-button" | ||
| > |
There was a problem hiding this comment.
Would it be possible to make this CSS class name more consistent with others in the component, e.g., components-palette-edit__menu-button
There was a problem hiding this comment.
good point - have made this change
ramonjd
left a comment
There was a problem hiding this comment.
This works as advertised and, as others have noted, is already a nice improvement.
I just added some notes about rejigging the class name to match the component's existing naming.
db7de8a to
a388d9e
Compare
|
Thanks for the review, @ramonjd, I have changed the class name as suggested. |
…36842) * Move changes to the new palette edit component * Remove redundant style * Change class name to match existing Co-authored-by: Glen Davies <glen.davies@a8c.com>



Description
Moves the
Edit colorsbutton from the ellipsis to a standard menu item to reduce confusion around the UI for editing custom colors.Immediate fix for #36519 ahead of wider redesign of this panel.
How has this been tested?
Remember, as noted in #36519 this is not intended to be the full and final fix, but a quick update to reduce confusion ahead of more detailed UX fixes.
Screenshots
Before:
After: