time to play the web’s hottest new game: is it a skeleton loading screen OR an invisible web font
-
-
./woff2metrics OpenSans-Regular.woff2 OpenSans-Regular.woff2m
@font-face { font-family: "Open Sans"; src: url("/fonts/OpenSans-Regular.woff2"); metrics: url("/fonts/OpenSans-Regular.woff2m"); } -
oh, as a completely new thing—yeah I could definitely see the value of that. I think it ties into a much larger discussion on the ability to partially-load fonts as part of a new format.
End of conversation
New conversation -
-
-
Oh, hmm—that’s an interesting idea. Metrics-only may be super small but it’d still render as invisible text, if I understand you correctly. You’d minimize/prevent reflow but at the cost of fallback text. It’d be a much worse failure case
-
What do you mean by your last two sentences?
- Show replies
New conversation -
-
-
Early versions of @.font-face rule had a descriptor to specify glyph widths right in the CSS, before downloading the font data. https://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#synthesizing … It'd be most helpful to progressively apply actual fonts as they're downloaded/decompressed. Not sure if it's possible in WOFF2.
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.