- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2022 16:35:43 +0000
- To: public-css-archive@w3.org
I discussed a similar issue with @emilio at TPAC and the problem is that most, but not all, of [to serialize a CSS value](http://w3c.github.io/csswg-drafts/cssom-1/#serializing-css-values) for colors moved to CSS Color 4. The part that remains, and thus makes reading CSS Color 4 about serialization, is: > If [<color>](https://w3c.github.io/csswg-drafts/css-color-4/#typedef-color) is a component of a **specified** value, then return the color as follows: > > - If the color was **explicitly specified** by the author, then return the original, author specified color value. > - Otherwise, return the value that would be returned if the color were a component of a computed value. That needs to be moved over; in addition, the rule in CSSOM does not reflect what browsers do and needs to be amended to > - If the color was **explicitly specified** by the author _as a named color_, then return the original, author specified color value folded to ASCII-lowercase. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7870#issuecomment-1277889963 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 October 2022 16:35:44 UTC