W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [css3-fonts] moving font load events to a separate spec

From: Glenn Adams <glenn@skynav.com>
Date: Tue, 19 Feb 2013 08:24:33 -0700
Message-ID: <CACQ=j+fsA8R-zNHZ2GLQ--okWT1ixuKeBDNhgu6SHihLDEddHg@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: www-style list <www-style@w3.org>
On Mon, Feb 18, 2013 at 10: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?
> Cheers,
> John Daggett
> [1] http://dev.w3.org/csswg/css3-fonts/#font-load-events
> [2] https://github.com/slightlyoff/DOMFuture/
+1, and suggest you rename to CSS3 Font Loader, since this material is more
than just events, e.g., loadFont() and checkFont() go beyond event
Received on Tuesday, 19 February 2013 15:25:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 12:35:22 UTC