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

Re: [css21] 'font-family' should disallow 'inherit' in font names more strictly

From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Date: Wed, 25 Apr 2012 01:10:47 +0800
Message-ID: <4F96DE97.7000406@csail.mit.edu>
To: Gérard Talbot <www-style@gtalbot.org>
CC: John Daggett <jdaggett@mozilla.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, WWW Style <www-style@w3.org>
(12/04/25 1:04), Kang-Hao (Kenny) Lu wrote:
> (12/04/25 0:23), "Gérard Talbot" wrote:
>> Le Mar 24 avril 2012 5:30, Kang-Hao (Kenny) Lu a écrit :
>>> (12/04/24 14:02), John Daggett wrote:
>>>> Tab Atkins Jr. wrote:
>>
>>>>>> The keywords 'initial' and 'default' are reserved for
>>>>>> future use and must also be quoted when used _in_
>>>>>> font names.
>>>>
>>>> This is equally imprecise, it implies that only the keywords are
>>>> quoted when what you mean to say is that font family names
>>>> *containing* these keywords must be quoted.
>>>
>>> Either that or
>>>
>>>   | unquoted global keywords ('inherit', 'initial' and 'default') are
>>>   | not allowed inside <family-name>.
>>
>>
>> div {font-family: inherit;}
>>
>> is allowed, is valid, is permitted and is tested:
> 
> Well, I said "inside <family-name>", so if the "Value:" field is
> "<family-name> | inherit", even if 'inherit' doesn't match <family-name>
> because of proposed wording, it still matches the right hand side.
> 
> Having said that, since you found this confusing, what about
> 
>   | unquoted global keywords ('inherit', 'initial' and 'default') are
>   | not allowed when parsed as <family-name>.
> 
> ?

I meant to say s/when parsed as <family-name>/when parsing <family-name>/


Cheers,
Kenny
Received on Tuesday, 24 April 2012 17:11:19 GMT

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