- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 21 Feb 2013 10:47:37 +0000
- To: Ian Hickson <ian@hixie.ch>
- Cc: WHATWG <whatwg@lists.whatwg.org>, John Daggett <jdaggett@mozilla.com>, Jonas Sicking <jonas@sicking.cc>
On Thu, Feb 21, 2013 at 5:59 AM, Ian Hickson <ian@hixie.ch> wrote: > On Wed, 20 Feb 2013, Jonas Sicking wrote: >> We could possibly still use the the FontLoader interface if we do the following: >> * FontLoader needs to drop the dependency on CSSFontFaceRule (or at >> least make the dependency optional and not available in workers). >> * We'll expose a global FontLoader object per worker scope. >> * The worker can't use any downloaded fonts other than the ones loaded >> through the global FontLoader for that scope. > > My expectation was that this is how FontLoader would work for workers. (We > can't rely on what fonts are in the Document since that's shared state, > and workers try to avoid shared state as a design principle.) Sure, but FontLoader is tightly coupled with the document since it does not actually supply URLs for the fonts itself, it relies on @font-face for that. It just indicates whether the font is loaded or that it should be loaded. -- http://annevankesteren.nl/
Received on Thursday, 21 February 2013 10:48:06 UTC