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

Re: [css-fonts] grammar changes for @font-face and @font-feature-values rules

From: John Daggett <jdaggett@mozilla.com>
Date: Mon, 29 Apr 2013 22:44:43 -0700 (PDT)
To: www-style list <www-style@w3.org>
Message-ID: <80207723.11659769.1367300683618.JavaMail.root@mozilla.com>
I've updated the CSS3 Fonts draft based on Simon's feedback.

> AFAICT, the point of <descriptor_declaration> is to not have the <prio>
> production for !important. You could, like @supports, refer to
> <declaration> defined in the Core Grammar instead.

Does @supports specifically ban the <prio> production?  I don't see the language in there for that.  It's a relatively minor point but I added the production to be clear that '!important' has no function in @font-face rules (there have been issues brought up in the past in relation to this).

> Whenever the grammar has S+, consider using S* instead. The
> difference is observable when using comment to separate tokens
> without whitespace:
> 
>      @font-feature-values Jupiter/**/Sans {}
> 
> We did require whitespace (ie. use S+) around operators in @supports
> and calc(), but I think this should be the exception rather than the
> rule. In this case, I think the most important is to be consistent
> with the 'font-family' property. Quick testing shows that this is
> messy in implementations, I’ll start another thread …

It is indeed a bit of a mess.  I've been putting together a set of tests for font family name parsing:

http://people.mozilla.org/~jdaggett/tests/test_font_family_parsing.html

I'll try and include the IDENT/**/IDENT case that you highlighted.

Cheers,

John
Received on Tuesday, 30 April 2013 05:45:10 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:10 UTC