- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Thu, 23 Apr 2026 23:00:08 +0000
- To: public-css-archive@w3.org
I think the current behavior is expected and more consistent. System colors do the same fwiw, and there's good reasons for that, see https://github.com/w3c/csswg-drafts/issues/6773 for a lot of discussion around that. I agree that for custom properties that define design-token-like things in particular (which are predominantly inherited) it's a bit unfortunate tho, but I believe the right thing there would be a bit different (and right now to get the behavior you want you just... don't type the property?). I.e., I don't see this as more unexpected than: ```css --unregistered-foo: 10em; --registered-foo: 10em; ``` Where `--registered-foo` gets "fixed" at 160px on the root for example. When you want to define a "design token"-like thing, you don't really want to define a computed color, you really want a specified value. There's no great way right now of getting the syntax checking benefits of typed properties without also having to opt into computing the value "eagerly", and I'm not sure how that'd look like, but I believe that's a larger-scope problem than light-dark. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13836#issuecomment-4308880778 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 April 2026 23:00:09 UTC