-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Open
Labels
Global StylesAnything related to the broader Global Styles efforts, including Styles Engine and theme.jsonAnything related to the broader Global Styles efforts, including Styles Engine and theme.json[Status] Needs More InfoFollow-up required in order to be actionable.Follow-up required in order to be actionable.[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended
Description
Description
While custom CSS appears to be enabled in WordPress 7.0,
it does not function properly with older original blocks lacking block.json.
Please consider either providing backward compatibility support or disabling customCSS entirely.
Step-by-step reproduction instructions
For original blocks without block.json,
the custom CSS input field appears.
Entering CSS works in the admin interface, but viewing the code editor shows the CSS is not applied.
Since the CSS is not applied on the frontend, the display is not correct.
Screenshots, screen recording, code snippet
No response
Environment info
WordPress 7.0-alpha
Theme Twenty Sixteen
Please confirm that you have searched existing issues in the repo.
- Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
- Yes
Please confirm which theme type you used for testing.
- Block
- Classic
- Hybrid (e.g. classic with theme.json)
- Not sure
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Global StylesAnything related to the broader Global Styles efforts, including Styles Engine and theme.jsonAnything related to the broader Global Styles efforts, including Styles Engine and theme.json[Status] Needs More InfoFollow-up required in order to be actionable.Follow-up required in order to be actionable.[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended
Type
Projects
Status
❓ Triage