You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is no longer valid for the Fonts API once the Font Library is merged.
Why?
As shared in Ongoing Roadmap update #41479 (comment), the Fonts API will no publicly expose the means to "register" or "enqueue" fonts. The Font Library and font management will handle the user workflow.
The Fonts API will get / pull the font variations from Theme JSON merged data that need their @font-face generated and printed.
What problem does this address?
Since weights can be a range, it would make sense for any weight within the range of the registered font face to be enqueued.
For example:
Font weight range from 200 to 900 gets registered. But right now, if you try passing a font weight within this range, you get an error:
What is your proposed solution?
Passing a font weight within the range (200 to 900) should enqueue that registered face.
In
theme.json
:The text was updated successfully, but these errors were encountered: