-
Notifications
You must be signed in to change notification settings - Fork 165
Default font Noto serif is still loading in the editor #700
Comments
I'm not actually sure! It's probably okay to dequeue it, but we should (obviously) test it out. |
I don't think we can, actually. https://github.com/WordPress/gutenberg/blob/1ee20134ada0415c3affe681e0c68cd19d2668c5/lib/client-assets.php#L398 Anyone? I opened an issue for Gutenberg. But I think we should, unless we would get in trouble for any locale. But I suppose that system fonts are properly equipped for all languages. |
@Hunter74: Can you clarify exactly what you're seeing? I'm not able to reproduce this. Twenty Nineteen does not call for Noto Serif at all, so I don't think this would be related to the theme. |
i am sorry it was the animate blocks plugin doing that |
Thanks for the issue, @LittleBigThing. Since I don't believe we can do anything about this until Gutenberg gives us an opportunity to dequeue the font, I'm going to close this issue rather than port it over to Trac. If WordPress/gutenberg#12611 gets resolved, we can add a new ticket to Trac and take care of it then. Thank you! |
Ok, thanks! |
Although the editor is styled to match the frontend of the site, including fonts, the default font Noto serif is still loaded in the editor.
Can we dequeue it?
Related to #181.
The text was updated successfully, but these errors were encountered: