- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jan 2020 22:35:25 +0000
- To: public-css-archive@w3.org
I wasn't there in person, and AIUI this issue will be discussed again tomorrow, which is great. In the meantime, I'd like to repeat the three driving use-cases from my perspective: 1. Provide a simple way for developers to make sure important, locally-cached web fonts apply on first render of the page, and to allow for this possibility if the font network request returns quickly. 2. Maximize speed of the final loaded state of pages that use web fonts, by avoiding two renders on load 3. Provide a way for sites to minimize [layout instability](https://wicg.github.io/layout-instability/) as it relates to web fonts, without large negative performance impact (**) (*) Note: this does *not* say anything about cases where the font is not available locally on the device. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-577910219 using your GitHub account
Received on Thursday, 23 January 2020 22:35:27 UTC