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 13:27:09 +0800
Message-ID: <CACQ=j+cXoVtB_rqwp9L9Hs+23Ei-RS2h_Ln73Mb61VGesy48ww@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: www-style list <www-style@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>
On Fri, Sep 7, 2012 at 12:39 PM, John Daggett <jdaggett@mozilla.com> wrote:

> Glenn Adams wrote:
>
> > I fail to see the relation between load completion and layout
> > completion. FontLoader should not be sensitive to layout state, just
> > font loading state. Again, I don't see a use case for the notify
> > method as has been described thus far. I'd prefer to discuss on this
> > ML for the record.
>
> Font loads occur due to layout measuring text, which runs font
> matching, which selects faces for a given run of text, which determines
> whether fonts need to be loaded or not.  Font loads do not occur if
> @font-face rules are defined but never used, that's why font loading
> depends upon layout behavior.
>

Yes, I understand all of that. It seems like you may be conflating
allcomplete with both (1) the layout processing (that may or may not
trigger a font load) and (2) actual font load processing. If that is the
case, then I think FontLoader is a bad place to anchor functionality
related to layout related events.
Received on Friday, 7 September 2012 05:27:58 GMT

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