- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 14:18:26 +0000
- To: public-css-archive@w3.org
> I'm happy to hold off shipping `light-dark()` on Firefox if people thing it's fundamentally wrong, or a step in the wrong direction that would prevent us from doing something that we might want like extending `color-scheme` to support custom author-provided palettes, somehow, but I don't think it's the case. The sentiment on social media ([X](https://x.com/bramus/status/1711488907014021267?s=20), [Mastodon](https://front-end.social/@bramus/111207106600754624)) is generally in favor. Recurring comments I’ve heard are: - What about high contrast? As @emilio mentioned this is orthogonal to light/dark mode, as you can have high/low contrast versions of each - What about other `color-scheme` values? [The spec](https://drafts.csswg.org/css-color-adjust-1/#color-scheme-prop) has built-in wiggle room to eventually allow these in the future, but reality is that [these are currently not allowed](https://drafts.csswg.org/css-color-adjust-1/#used-color-scheme:~:text=%3Ccustom%2Dident%3E%20values%20are%20meaningless%2C%20and%20exist%20only%20for%20future%20compatibility). These issues seems both unrelated to `light-dark()` itself. > @emilio @bramus was the intent to exclude `light-dark()` from use in `override-colors`? Or was that unintentional and I should move it? I can’t gauge the consequences of doing that, so I’ll leave that decision up to Emilio and one of the color experts here – a certain Chris, I think you know him ;) – to make. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7561#issuecomment-1755522437 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 14:18:28 UTC