On Tue, May 27, 2014 at 3:47 PM, Jonas Sicking wrote:
> On Tue, May 27, 2014 at 12:14 PM, Tab Atkins Jr. wrote:
>> On Tue, May 27, 2014 at 11:44 AM, Jonas Sicking wrote:
>>> On Tue, May 27, 2014 at 10:41 AM, Tab Atkins Jr.
>>> wrote:
> Separately, FontFace.loaded seems to fulfill the same
On Tue, May 27, 2014 at 12:14 PM, Tab Atkins Jr. wrote:
> On Tue, May 27, 2014 at 11:44 AM, Jonas Sicking wrote:
>> On Tue, May 27, 2014 at 10:41 AM, Tab Atkins Jr.
>> wrote:
Separately, FontFace.loaded seems to fulfill the same purpose as
FontFaceSet.ready(). I.e. both indicate that
On Tue, May 27, 2014 at 11:44 AM, Jonas Sicking wrote:
> On Tue, May 27, 2014 at 10:41 AM, Tab Atkins Jr. wrote:
>>> Separately, FontFace.loaded seems to fulfill the same purpose as
>>> FontFaceSet.ready(). I.e. both indicate that the object is done
>>> loading/parsing/applying its data. It seems
On Tue, May 27, 2014 at 10:41 AM, Tab Atkins Jr. wrote:
>> Separately, FontFace.loaded seems to fulfill the same purpose as
>> FontFaceSet.ready(). I.e. both indicate that the object is done
>> loading/parsing/applying its data. It seems more consistent if they
>> had the same name, and if both we
On Tue, May 27, 2014 at 1:22 AM, Jonas Sicking wrote:
> I've provided this input through a few channels already, but I don't
> think the user of [SetClass] here is good (and in fact I've been
> arguing that SetClass should be removed from WebIDL).
Yes, there's an issue in the spec already saying
niel.glaz...@disruptive-innovations.com>; Domenic
Denicola<mailto:dome...@domenicdenicola.com>
Cc: cha...@w3.org<mailto:cha...@w3.org>;
public-webapps<mailto:public-webapps@w3.org>;
public-webfonts...@w3.org<mailto:public-webfonts...@w3.org>
Subject: Re: Last Call for &qu
I've provided this input through a few channels already, but I don't
think the user of [SetClass] here is good (and in fact I've been
arguing that SetClass should be removed from WebIDL).
First off you likely don't want to key the list of fonts on the
FontFace object instance like the spec current
