-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor styles are applied inconsistently for themes that do not support theme.json #35730
Comments
Hey, thanks for reporting. I can indeed confirm that removing this check has caused this bug. I'm a bit puzzled as to why, though. My best hypothesis at the moment is that removing this check has surfaced at an existing bug that was dormant. I checked and, for the Nucleare theme, if the |
Created a second PR at #35737 I think this is a better approach, but would like to hear people's thoughts. |
As soon as I upgraded the Gutenburg plugin to the latest 11.7.1 , from the previous version 11.6.0, the fonts displayed in the editor no longer match my theme fonts, they seem to have reverted to some default fonts (see attached picture). I don't like it at all because I like my theme fonts, so I will be reverting to the previous version of Gutenburg, until this is fixed. |
Description
If a theme does not support theme.json, editor styles are not applied on some themes, and text is rendered in the browser's default font.
This appears to have been introduced in #35424, when the check for
WP_Theme_JSON_Resolver_Gutenberg::theme_has_support()
was removed.In testing a few different themes, it does appear there are theme-specific variables at play as well, and not simply whether or not the theme supports theme.json. How and when the theme declares its editor styles may be a factor (ie
add_editor_style()
vswp_enqueue_style(
) and/orinit
vsenqueue_block_editor_assets
for example)Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
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
The text was updated successfully, but these errors were encountered: