Skip to content
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

Livro: Newsreader font is no longer loaded #5705

Closed
markhowellsmead opened this issue Mar 18, 2022 · 4 comments
Closed

Livro: Newsreader font is no longer loaded #5705

markhowellsmead opened this issue Mar 18, 2022 · 4 comments

Comments

@markhowellsmead
Copy link

Steps to replicate

The Newsreader font is still defined in CSS but the font file/s are no longer loaded.

Result

The website typography appears in the standard browser fallback serif font.

Expected

The Newsreader fonts in the assets folder should be loaded by the theme.

@jffng
Copy link
Contributor

jffng commented Mar 18, 2022

Thanks for the report, we just made the switch to load the fonts via theme.json since Gutenberg was upgraded, my guess is this is an artifact of some caching.

Newsreader is loading on the demo site, so I'm going to close this:

Screen Shot 2022-03-18 at 11 44 57 AM

@jffng jffng closed this as completed Mar 18, 2022
@markhowellsmead
Copy link
Author

@jffng Font still not loading even with caching disabled on the site and it's running the latest version of the theme (1.0.9). There is no reference in the source code to the WOFF files. If I look at the documentation for theme.json, there is no reference that the src attribute is supported for fontFamilies.

@jffng
Copy link
Contributor

jffng commented Mar 21, 2022

The Webfonts API was recently added WordPress/gutenberg#37140, and the theme.json documentation needs to be updated accordingly. This feature is not in core yet, are you running the Gutenberg plugin?

@markhowellsmead
Copy link
Author

markhowellsmead commented Mar 21, 2022

No, I'm using the Theme directly from https://wordpress.org/themes/livro/. The Gutenberg plugin is highly unstable and often breaks functionality, so it's not possible to use it on a production site. I'm guessing that this issue is happening for the 200+ other non-WordPress.com users too, unless they're using the plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants