- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2020 18:29:01 +0000
- To: public-css-archive@w3.org
Yeah, the "load/use all the faces of this font, or none of them" is a reasonable thing to want, but it's definitely an orthogonal issue; you'd want that control for non-`optional` fonts as well. So unless there's an important connection to the current topic that I'm not seeing, I'd like to push that to another issue. > I still think we need to define how browsers render when they load fonts from disk. I've never seen this create layout stability issues, but maybe there are extreme cases where it does. Per @xiaochengh, loading from memory cache is always fine, but loading from disk cache sometimes (often?) misses the first frame's layout/painting, so the second frame has a layout jump. It might be that a single frame of jump is perfectly fine tho; I want to hear from people currently experiencing that (we've got some internal customers for this behavior, apparently), and if it's okay, make sure the spec text is flexible enough to allow for it. (Currently it's not; if you miss the first paint you'll never use the font. It just lets you delay the first paint a little if you want to give it a chance to finish loading.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-574309800 using your GitHub account
Received on Tuesday, 14 January 2020 18:29:03 UTC