- From: Jason Pamental via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2016 19:44:57 +0000
- To: public-css-archive@w3.org
The way it's done with the Web Font Loader (used by Typekit and Google Web Fonts, and Monotype does the same thing with Fonts.com, but with different classes) is something like this: 1) Insert 'loading' classes - one general, and one for each font that is loading 2) Monitor the loading process, swapping out the 'loading' classes for 'loaded' ones as each font loads 3) Finally swapping the general one once all are loaded. Additionally both methods (Web Font Loader and Fonts.com's version) supply an 'inactive' class, which is added with the 'loading' classes, and is meant to stay there in the event that the web fonts don't ever fully load. If they do, it is removed as well. While it would be great to have access to a 'loading' state for each font, the (perhaps) more helpful (and easier to set things across the board) is that general 'loading/loaded' state (all or none essentially). -- GitHub Notification of comment by jpamental Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/450#issuecomment-245394474 using your GitHub account
Received on Wednesday, 7 September 2016 19:45:12 UTC