Re: [css-color] Moving sections, and grammar for <color>

On 27/03/2014 18:14, Tab Atkins Jr. wrote:
> On Wed, Mar 26, 2014 at 3:15 PM, Simon Sapin <> wrote:
>> Hi,
>> In the current ED:
>> sections 4 to 10 each define some values of the <color> type. They should be
>> subsections of section 3 which defines <color>, so separate them form other
>> things this document defines. (The properties.)
> This sort of organization isn't a hard-and-fast rule,

I’m not saying it is, just that I thought it’d help readers.

> particularly in
> a spec that defines a *bunch* of values for the grammar term.  For
> example, Images defines different types of <image> in different
> top-level sections.  I think the ToC reads much better with things
> separated the way they are.  The properties are well-identified by
> their section names already.

Ok, I don’t feel strongly about this part.

>> Also, it’s not clear which of all the defined grammars are <color> values.
>> For example, it looks like hwb() is meant to be a <color>, but <named-hue>
>> is not. But I’m guessing here.
>> A grammar for <color> (near the beginning of section 3) should fix this.
>> Something like:
>>    <color> = rgb() | rgba() | hsl() | hsla() |
>>              <named-color> | transparent | currentcolor |
>>              hwb() | gray() | device-cmyk() | color()
> Ah, good point.  Fixed.

Great thanks.

Just one thing: you didn’t include 'transparent'. Is it part of 
<named-color>? (While currentcolor isn’t?)

Simon Sapin

Received on Thursday, 27 March 2014 19:01:29 UTC