- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Oct 2022 18:28:11 +0000
- To: public-css-archive@w3.org
I suppose authors could also use custom properties to clarify intents, and narrow down their list of 'options' in the same way they do with design tokens:
```css
html {
--perceptual: oklab;
--legacy: srgb;
--linear: xyz-d65;
}
```
By leaving that to authors, we avoid the issue of locking-in behavior long term. Is there a consensus developing towards allowing all spaces, and using examples/notes to help guide authors towards the reasons they might use one over another?
--
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7907#issuecomment-1289424286 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 October 2022 18:28:13 UTC