W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

Re: [csswg-drafts] [css-fonts] Address missing aspect of Progressive Enhancement in font loading

From: Jason Pamental via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Sep 2016 21:20:45 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-245423133-1473283243-sysbot+gh@w3.org>
@litherum -

There's no way to be 100% perfect, but in general the fallback stack 
should be fairly well supported, and you'd generally want to optimize 
for the most widely available (or most likely 'first alternate': Arial
 or Helvetica on most desktops, Droid on Android - whichever comprises
 the largest segment of your audience).

So I generally define a set of fallbacks that will cover the basics 
and optimize for the first one in the stack. It's not perfect, but far
 better than doing nothing in terms of getting content on screen and 
minimizing reflow when the fonts load.

If this is tied in some way to the Font Loading API, then the behavior
 could simply follow however that is working: if the boolean flag is 
in the 'loading' state for all @font-face blocks then 'loaded=false'; 
if they're all 'loaded' then 'loaded=true' (I'm imagining this as an 
attribute selector, but hopefully you get what I mean in a more 
general sense)

-- 
GitHub Notification of comment by jpamental
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/450#issuecomment-245423133 
using your GitHub account
Received on Wednesday, 7 September 2016 21:20:52 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:34 UTC