Closed HereChen closed 5 years ago
How would this change affect browsers that don't support this feature?
@daveliepmann
This change has no effects on browsers that don't support it.
So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported property values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored. Partial Implementations
https://css-tricks.com applied this feature even though IE 11 does not support font-display
.
This article font-display
for the Masses may help you understand the problems font-display
solved.
See #119 for prior report.
Thanks for the recommendation; we're trying it out.
Font loading has a performance issue. And set
font-display: swap
is not possible with CDN.Is it possible to set
font-display: swap
as default?see also Suggestion: Implement font-display, Ensure text remains visible during webfont loads.