Re: [csswg-drafts] [css-color-4] Serialization of named colors (#7870)

> `<system-color>`, `<deprecated-color>`, `currentColor`, `transparent`, as components of a specified value, also serialize to the (all lowercase) named value in Chrome/FF.

Right, though the section you are quoting from is about sRGB colors. `transparent` and `currentColor` are dealt with in [Resolving other colors](https://drafts.csswg.org/css-color-4/#resolving-other-colors), and `currentColor` is not necessarily an sRGB color. 

(`transparent` is, though, and should probably be added to [Resolving sRGB values](https://drafts.csswg.org/css-color-4/#resolving-sRGB-values)).  CSS Color 3 only defined the [**computed** value of transparent](https://www.w3.org/TR/css-color-3/#transparent). Is there value in retaining whether the author used `transparent` or `rgba(0,0,0,0)`? I don't have a strong opinion either way, so would follow what implementations currently do.

There is a contradiction in the spec regarding whether system colors are sRGB colors, see 
 - https://github.com/w3c/csswg-drafts/issues/8312

-- 
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7870#issuecomment-1385393593 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 January 2023 13:04:06 UTC