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

Re: [css-fonts] defining font faces with an empty or white space only family name

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 7 Jul 2014 15:45:00 -0700
Message-ID: <CAAWBYDCTMTyLbNWnUm1oS+BSVJGXAyVa439nH7d+HmUJikfzog@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: "www-style@w3.org" <www-style@w3.org>
On Mon, Jul 7, 2014 at 3:44 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> On 08/07/14 08:31, Tab Atkins Jr. wrote:
>> Whoops, I totally misread what you were asking, and then talked about
>> it in a confusing way.  I didn't realize you were talking about actual
>> CSS strings, specifically an empty string or a whitespace-only string.
>>
>> Both of those should be valid, per the current spec.
>
> OK.  Should they be? :-)  At least for the empty string, given that
> implementations seem to agree that the @font-face isn't defined, can we make
> that an error that causes the rule to be ignored (just like the lack of a
> font-family or src descriptor)?  And therefore |new FontFace("''", ...)| as
> well.

While I'm willing to match implementations, I don't think there's any
compat we have to worry about here.  I'm more curious about whether
the impls have a *reason* for considering that invalid or not.

~TJ
Received on Monday, 7 July 2014 22:45:52 UTC

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