Make WordPress Core

Opened 2 years ago

Closed 2 years ago

Last modified 19 months ago

#58090 closed defect (bug) (reported-upstream)

Global Styles custom colors with the same name are not differentiated

Reported by: plari's profile plari 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

  1. Start in site editor
  2. Select global styles
  3. Colors>Palettes>Custom Colors, add custom colors
  4. Select "Show Details" in the menu for custom colors, and rename all the colors to the same name, such as "Color 1"
  5. 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.

https://user-images.githubusercontent.com/27249804/229915405-2084f947-9bcc-4153-8dd9-3c0becc76504.png

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)

Markup on 2023-04-04 at 13:37:48.png (227.4 KB) - added by plari 2 years ago.
Screenshot of result of Custom Colors all using the same name

Download all attachments as: .zip

Change History (4)

@plari
2 years ago

Screenshot of result of Custom Colors all using the same name

#1 @plari
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 @plari
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

#3 @desrosj
19 months ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.