Customizer: Custom Colors don't consider chosen palette
Open
Nobody has claimed this yet.
customer report
enhancement
- Dominant language
- PHP
- Stars
- 306
- Forks
- 88
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 12
Description
Description
When adding a custom color, the defined value will be set for / used by all palettes.
Expected behaviour is to be able to set the value for each palette individually.
Step-by-step reproduction instructions
Assuming having palettes Base and Dark Mode
- In Customizer, go to Colors and Background
- Select Base palette if not already chosen (optional)
- In section Custom Colors add a custom color and set any value
- Publish changes
- Switch to Dark Mode palette
- Modify the color value for the newly added custom color
- Publish changes
- Switch back to Base palette
- Notice that the value from Dark Mode palette was applied to Base palette, too
Screenshots, screen recording, code snippet or Help Scout ticket
No response
Environment info
No response
Is the issue you are reporting a regression
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Customizer under Colors and Background using the Base and Dark Mode palettes. Trace how the newly added custom color is stored and loaded when switching palettes; done means changing the value in one palette no longer changes it in the other.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- design, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100