- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Dec 2023 19:06:49 +0000
- To: public-css-archive@w3.org
> I don’t think these should exclude each other.
Oh, they were never intended to. A color scheme is a color scheme, if we have `schemed-color()` then yeah you can refer to a custom scheme in there.
What I still don't actually understand, tho, is what your original example is intending to do. I don't see anything activating a color scheme, nor any definition of what those three custom color schemes are. Are they intended to be literally meaningless outside of their ability to trigger `schemed-color()`? That's not workable - the color scheme defines the system colors, so we still need to know *at minimum* which built-in scheme to use for them (aka the `@color-scheme --foo { base-scheme: light; }` part of my proposal). And then letting you override those colors is just an obvious extension.
I might be missing something obvious about how you're intending that first example to behave, tho.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9660#issuecomment-1841452919 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 December 2023 19:06:52 UTC