- From: Stephen Zilles <szilles@adobe.com>
- Date: Mon, 18 Feb 2013 21:46:27 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, John Daggett <jdaggett@mozilla.com>
- CC: www-style list <www-style@w3.org>
+1 Steve Z. -----Original Message----- From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] Sent: Monday, February 18, 2013 9:34 PM To: John Daggett Cc: www-style list Subject: Re: [css3-fonts] moving font load events to a separate spec On Mon, Feb 18, 2013 at 9:27 PM, John Daggett <jdaggett@mozilla.com> wrote: > > Last fall, after some discussions on www-style, I included a > definition of an interface for font load event handling in CSS3 Fonts [1]. > Since then, I've poked various people to look this over and two issues > have come up that I think require more thought: > > 1) Given that the FontLoader object is defined to be attached to the > document, how will canvas worker threads load fonts? > > 2) Some FontLoader methods, in particular loadFont, seem like a good > fit for DOMFuture [2], a spec that hopefully will be ready within > the next month or so. Should FontLoader be based on that or at > least some parts of that? Do we need to decide this now? > > I'd like to move CSS3 Fonts to LC but I think the FontLoader portion > requires more consideration. Rather than hold up the long overdue CSS3 > Fonts spec, I'd like to propose splitting out the font load events > portion into a separate spec, with the intention of bringing that to > LC within a couple months once the issues outlined above have been > discussed more thoroughly. > > So my proposal is to move font load events out into "CSS3 Font Load Events". > > Thoughts? Given the need for further baking/syncing with other specs that aren't yet ready, I support splitting this out. ~TJ
Received on Tuesday, 19 February 2013 05:46:52 UTC