W3C home > Mailing lists > Public > www-style@w3.org > September 2012

Re: [css3-fonts] rethinking font load events

From: Glenn Adams <glenn@skynav.com>
Date: Fri, 7 Sep 2012 10:22:27 +0800
Message-ID: <CACQ=j+ftMdsEei-AsGqoS3czTcAMC+Y44oVfmAmeeMrseggtZQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: John Daggett <jdaggett@mozilla.com>, www-style list <www-style@w3.org>
On Fri, Sep 7, 2012 at 9:08 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Thu, Sep 6, 2012 at 6:03 PM, Glenn Adams <glenn@skynav.com> wrote:
> > On Thu, Sep 6, 2012 at 10:10 PM, John Daggett <jdaggett@mozilla.com>
> wrote:
> >>
> >>
> >>   // notify completion, even if no fonts load
> >>   void notifyAfterCompletion();
> >
> > The utility of this method seems particularly questionable. What should
> a UA
> > do when this is called?
>
> If FontLoader.readyState is "loading", nothing.
>
> If it's "idle", fire an "allcomplete" event anyway.
>

Then what is the point? Why have the client code call a method to that only
translates to firing allcomplete when the client code can invoke the same
allcomplete handler?


> I explained the utility of it in my last message.
>

I read it, but it didn't explain its utility as far as I can tell. What
does the UA do different when/whether the notify is called?
Received on Friday, 7 September 2012 02:23:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:59 GMT