- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 27 Mar 2014 11:14:44 -0700
- To: Simon Sapin <simon.sapin@exyr.org>
- Cc: www-style list <www-style@w3.org>
On Wed, Mar 26, 2014 at 3:15 PM, Simon Sapin <simon.sapin@exyr.org> wrote: > Hi, > > In the current ED: > > https://dvcs.w3.org/hg/csswg/raw-file/931f8a9374a1/css-color/Overview.html > > 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, 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. > 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. ~TJ
Received on Thursday, 27 March 2014 18:15:33 UTC