- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2020 23:15:05 +0000
- To: public-css-archive@w3.org
> As you mentioned earlier, optional is for low priority fonts. It looks pretty hacky to use preload + optional to handle high priority fonts. What you described isn't high priority, tho! You described a situation where a font that takes longer than 100ms never gets used. That's clearly still an "optional" font; it's nice-to-have but not vital. `optional` is intended to prioritize the user experience (no layout jumping) over the authoring design intent (pretty fonts). If the author does nothing else, it can also prioritize the user's bandwidth, but that's listed as a secondary, very much optional additional effect. Preloading is a common and reasonable technique where we let the author control the user experience a little (kicking off downloads eagerly) in return for a hopefully better UX later (things being visible immediately when used). Combining the two seems totally reasonable to me. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-573242378 using your GitHub account
Received on Friday, 10 January 2020 23:15:07 UTC