#58090 closed defect (bug) (reported-upstream)
Global Styles custom colors with the same name are not differentiated
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.2 |
Component: | Editor | Keywords: | |
Focuses: | Cc: |
Description
If custom colors are added in the global styles theme settings with the same name (eg Color 1), it becomes impossible to select any color but the last custom color of that name.
Steps to reproduce
- Start in site editor
- Select global styles
- Colors>Palettes>Custom Colors, add custom colors
- Select "Show Details" in the menu for custom colors, and rename all the colors to the same name, such as "Color 1"
- Return to the editor, and try selecting one of these custom color for any block color setting
Result
Of the Custom colors have the same name, the editor interface displays the last color of that name, while the color picker itself shows the first color of that name, even if something between those two is selected.
Possible Solution
Preventing Custom Colors from being given the same name would help alleviate this issue.
Originally reported here: https://github.com/Automattic/wp-calypso/issues/75197
Replicated in WP version 6.2 with all plugins deactivated.
Theme: Twenty Twenty-Three
Attachments (1)
Change History (4)
#1
@
2 years ago
- Summary changed from Global Styles custom colors with the same name to Global Styles custom colors with the same name are not differentiated
#2
@
2 years ago
- Resolution set to reported-upstream
- Status changed from new to closed
Reported in Gutenberg GitHub Repository instead: https://github.com/WordPress/gutenberg/issues/49593
Screenshot of result of Custom Colors all using the same name