[wp-trac] [WordPress Trac] #60151: FSE theme Styles select Issue
WordPress Trac
noreply at wordpress.org
Thu Feb 15 06:15:18 UTC 2024
#60151: FSE theme Styles select Issue
--------------------------+------------------------------
Reporter: tazeenehsan | Owner: (none)
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: Awaiting Review
Component: Editor | Version:
Severity: normal | Resolution:
Keywords: | Focuses: ui
--------------------------+------------------------------
Comment (by tsbkdgwi71):
Thank you for bringing this issue to our attention. It seems like there is
a bug in the handling of color presets in the Gutenberg block editor.
Based on your description and the provided image, it appears that when
selecting the "custom" color option, both the "custom" and "secondary"
options are being visually selected, but only the "secondary" option is
being saved in the backend.
This behavior is unexpected and can lead to confusion for users who intend
to select the "custom" color option but end up with the "secondary" color
instead.
To address this issue, it's necessary to investigate the root cause of the
problem and implement a fix in the Gutenberg block editor code. Here are
some steps that can be taken to resolve the issue:
1. **Identify the Cause**: Review the code responsible for handling color
presets in the Gutenberg block editor to identify any logic errors or
inconsistencies that may be causing the issue.
2. **Debugging**: Use debugging tools such as browser developer tools or
logging statements to trace the flow of data and identify where the
discrepancy between the selected color option and the saved option occurs.
3. **Testing**: Create test cases to replicate the issue in a controlled
environment and verify that the fix resolves the problem without
introducing any regressions.
4. **Fix**: Once the root cause of the issue has been identified,
implement a fix in the Gutenberg block editor codebase to ensure that
selecting the "custom" color option correctly saves the chosen color
without interference from other presets.
5. **Documentation**: Update documentation or release notes to inform
users about the fix and any changes to the behavior of color presets in
the Gutenberg block editor.
6. **Release**: Once the fix has been implemented and tested, release an
updated version of the Gutenberg block editor with the fix included.
By following these steps, we can address the issue with the styling of
Gutenberg blocks when selecting custom color presets and ensure a smoother
user experience for WordPress users and developers alike. If you require
further assistance or clarification on any aspect of this issue, please
feel free to ask.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60151#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list