W3C home > Mailing lists > Public > www-style@w3.org > June 2014

Re: [css-font-loading] behaviour of setting FontFace family, style, etc. attributes

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 22 Jun 2014 08:12:29 -0700
Message-ID: <CAAWBYDC05+95c2ANe6EDzpKvGeYMrBv0Vm0YLuh6kySSjZvGdw@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: "www-style@w3.org" <www-style@w3.org>
On Sat, Jun 21, 2014 at 10:46 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> What should happen when assigning to the family, style, etc. attributes of a
> FontFace object?  Should it be something like the FontFace constructor,
> i.e.:
>   1. Set the status to "unloaded".  Run the remaining steps
>      asynchronously.
>   2. Parse the string as you would the corresponding @font-face
>      descriptor.  If it fails to parse, reject the status promise.
>      Otherwise, queue a task to set the attribute to the serialization
>      of the parsed value.
>   3. ...

Fixed now. It should just be done sync, and throw TypeErrors and do
nothing if it fails to parse.  No reason to actually unload the font.

> What about when the FontFace object is connected to an @font-face rule?
> When do you effectively set the descriptor on the rule?

The spec says "immediately", so synchronously with the change in the
object (and vice versa for changes in the rule).

Received on Sunday, 22 June 2014 15:13:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:43 UTC