This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
Adding a 'name' attribute to the Cardo font family definitions. #422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sing 'name' attribute causes the font resources to not render
MaggieCabrera
approved these changes
Sep 19, 2023
|
Thank you Jason! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With the latest Gutenberg release a 'name' attribute is required in font family definitions. I believe it has always been required, but the resources would still render. Now, if it is missing the
<style id='wp-fonts-local'...resource does not render.Testing Instructions
Ensure Gutenberg plugin is latest (/trunk) and active.
Render any view with the default 'Cardo' font applied.
Note that the font face resources are used.