- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 07:19:35 +0000
- To: public-houdini-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-typed-om-1] `currentColor` is not the only non-absolute color == In [6.7. Serialization from CSSOM Value](https://www.w3.org/TR/2024/WD-css-typed-om-1-20240321/#cssom-serialization), several times we read: > If the value is the [`currentcolor`](https://www.w3.org/TR/css-color-4/#valdef-color-currentcolor) keyword, return "currentcolor". > Otherwise, return the result of serializing the [`<color>`](https://www.w3.org/TR/css-color-5/#typedef-color) value. That isn't the only case for non-absolute colors. It would be better perhaps to reference CSS Color 5 [absolute color](https://www.w3.org/TR/css-color-5/#absolute-color) whose more comprehensive definition is: > An absolute color is a [`<color>`](https://www.w3.org/TR/css-color-5/#typedef-color) whose computed value has an absolute, colorimetric interpretation. This means that the value is not: > * [currentColor](https://www.w3.org/TR/css-color-4/#valdef-color-currentcolor) (which depends on the value of the [color](https://www.w3.org/TR/css-color-4/#propdef-color) property) > * a [`<system-color>`](https://www.w3.org/TR/css-color-4/#typedef-system-color) (which depends on the color mode) > * [`<light-dark()>`](https://www.w3.org/TR/css-color-5/#funcdef-light-dark) (which depends on the color mode) > * [`<device-cmyk()>`](https://www.w3.org/TR/css-color-5/#funcdef-device-cmyk) (which has no colorimetric basis) > Nor are any of those values used inside [<color-mix()>](https://www.w3.org/TR/css-color-5/#funcdef-color-mix) or in relative color syntax. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1125 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 07:19:37 UTC