Opened 7 months ago
Closed 7 months ago
#62765 closed defect (bug) (reported-upstream)
Color Option Available in Navigation Block Editor but Not in Global Site Styles
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | trunk |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
The color option is available when editing the Navigation Block directly within the block editor, but it is not available when accessing the Global Site Styles.
Users are unable to adjust the color settings for the Navigation Block through the Global Site Styles panel.
Steps to Reproduce:
- Appearance > Editor
- up right go to styles
- choose Blocks, then choose Navigation
- Try to adjust the color of the Navigation Block through Global Site Styles.
Notice that the color option for the Navigation Block is missing.
- Now Open the Block editor (up right - beside styles)
- Add or select the Navigation Block.
- Notice that the color option is available and can be modified through Block editor.
Expected Result: The color option for Navigation should be available in both the Block editor and the Global Site Styles for consistent styling.
Actual Result: The color option for Navigation is only available in the block editor and not in the Global Site Styles.
Attachments (2)
Change History (3)
Note: See
TracTickets for help on using
tickets.
Hi @rituchudasama thank you for the report and welcome to WordPress Trac!
Bugs and feature requests for blocks and the block editor are managed in the Gutenberg GitHub repository, and the issues need to be opened there and not on Trac.
-There is a message about this when you create a new ticket here on Trac, please let us know if there are ways this could be improved so that it is easier to know where to open the tickets.
It can also be helpful to think of missing features as enhancements, not bugs.
Color options for blocks are tracked in this issue:
https://github.com/WordPress/gutenberg/issues/43245
So in this case, no new ticket or issue needs to be created.
Because of this, I will close this ticket as "reported upstream"-