- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2020 21:14:04 +0000
- To: public-css-archive@w3.org
> However, we can't know whether a font is used without actually rendering the document. I don't understand what you mean here; this seems obviously false. You know when a font is used after *styling* a document; the render is much later in the pipeline. > So If authors want to ensure no extra rendering while maximizing the chance that the font is used, do they have to force loading it with Font Loading API or `<link rel="preload">`, in combination with optional? Yes. That'll give the page vital milliseconds to pull down the font (or load it from disk cache) before the page is otherwise renderable, maximizing the chance it gets selected. > The latest spec revision seems to solve the latter. Should we introduce something like font-display: important for the former? The `optional` value was *always* the latter; the name, the description, and the mechanics were all firmly aimed at "I'd like to use this font but it's *totally okay* to render the text in whatever's available quickly". `font-display: important` is just `font-display: block`, no? Or if it's not, that's because it's actually even *more* restrictive than `block`, blocking rendering of the *entire page* until the font is delivered (rather than just the text)? Given that we already widely agree that `block` is a bad, user-hostile behavior, I don't see how an *even more* hostile behavior would be something we want to add. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-573207814 using your GitHub account
Received on Friday, 10 January 2020 21:14:06 UTC