Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

Default font Noto serif is still loading in the editor #700

Closed
LittleBigThing opened this issue Dec 2, 2018 · 6 comments
Closed

Default font Noto serif is still loading in the editor #700

LittleBigThing opened this issue Dec 2, 2018 · 6 comments
Labels
question Further information is requested

Comments

@LittleBigThing
Copy link

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.

screenshot 2018-12-02 at 08 33 37

Can we dequeue it?

Related to #181.

@kjellr kjellr added the question Further information is requested label Dec 3, 2018
@kjellr kjellr added this to the 5.0.1 milestone Dec 3, 2018
@kjellr
Copy link
Collaborator

kjellr commented Dec 3, 2018

I'm not actually sure! It's probably okay to dequeue it, but we should (obviously) test it out.

@LittleBigThing
Copy link
Author

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.

@kjellr
Copy link
Collaborator

kjellr commented Dec 11, 2018

@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.

@ip2C
Copy link

ip2C commented Dec 11, 2018

@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

@kjellr kjellr removed this from the 5.0.2 milestone Dec 13, 2018
@kjellr
Copy link
Collaborator

kjellr commented Jan 10, 2019

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!

@kjellr kjellr closed this as completed Jan 10, 2019
@LittleBigThing
Copy link
Author

Ok, thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants