[csswg-drafts] [css-color-4][cssom] Overlap between the definition of resolving color values and serializing <color> component values.

frivoal has just created a new issue for 

== [css-color-4][cssom] Overlap between the definition of resolving 
color values and serializing <color> component values. ==
Forked from [a comment in another 

As discussed at the Seattle F2F, there is some overlap between 
https://drafts.csswg.org/cssom/#serialize-a-css-component-value and 

https://drafts.csswg.org/css-color-4/#resolving-color-values is more 
specific / clear about which color should resolve to what at what 
time, but cssom is more specific about how to serialize the various 
functions once you've decided to do that.

Fixing this redundancy by having css-color-4 just keep the high level 
logic, and defer to cssom for the string level details of how to 
serialize the value does not seem particularly good to me, as 
presumably the new functions added to css-color-4 (and later) will 
have their serialization in css-color-4 (and later), and then you need
 to look up to multiple specs to have the full picture.

What I think would be nicer is:
* inline the the details that currently live in cssom into css-color-4
* have css-color-4 normatively state that it supersedes cssom on this 
* either:
  * leave cssom as is, maybe with a note informatively pointing back 
to color-4)
  * make cssom normatively reference css-color-4 about this.

 The comment/issue at the bottom of this section of cssom seems to 
> One idea is that we can remove this section somewhere in the 
CSS3/CSS4 timeline by moving the above definitions to the drafts that 
define the CSS components.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/982 using your GitHub 

Received on Wednesday, 25 January 2017 04:31:41 UTC