- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Apr 2022 16:42:18 +0000
- To: public-css-archive@w3.org
As [proposed earlier](https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1069280421): So, in **4.7.5. Resolving other colors**, instead of > Each [`<system-color>`](https://drafts.csswg.org/css-color-4/#typedef-system-color) keyword computes to itself. Its used value is the corresponding color in its color space. we would have > Each [`<system-color>`](https://drafts.csswg.org/css-color-4/#typedef-system-color) keyword computes to the corresponding color in its color space. However, implementations which also implement [forced color mode]() must maintain an internal flag for such colors, to preserve the fact that they were specified as system colors and must not be forced. We would also need a change to [**4.8.6. Serializing other colors**](https://drafts.csswg.org/css-color-4/#serializing-other-colors) because currently, `<system-color>` keywords serialize as the lowercased name. They would now serialize as `rgb(nn, nn, nn)` [same as named colors](https://drafts.csswg.org/css-color-4/#serializing-sRGB-values), right? -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1098266205 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 April 2022 16:42:19 UTC