No way to specify font-display on @font-face
Chrome's Lighthouse suggests setting the `font-display` CSS property to deal with the trade offs between FOUT/FOIT and missing content and links to the following article: https://developers.google.com/web/updates/2016/02/font-display Unfortunately there doesn't appear to be a way to pass this configuration to `webfontloader` which I believe is responsible for assigning the `@font-face` definitions.
Posted by chillitom on Dec 3, 2018, 2:24 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
No way to specify font-display on @font-face
Chrome's Lighthouse suggests setting the `font-display` CSS property to deal with the trade offs between FOUT/FOIT and missing content and links to the following article: https://developers.google.com/web/updates/2016/02/font-display Unfortunately there doesn't appear to be a way to pass this configuration to `webfontloader` which I believe is responsible for assigning the `@font-face` definitions.
Comments (0)
No comments yet. Start the discussion.