- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Fri, 15 May 2026 13:58:43 +0000
- To: public-css-archive@w3.org
@romainmenke > I do think that it is too late to make a change here. > This feature has been in browsers for 2 years. I covered this in the OP: > Is it **web compatible**? [Per ChromeStatus](https://web-platform-dx.github.io/web-features-explorer/features/light-dark/) `light-dark()` as a whole is used on **1.23%** of page loads, though the number is climbing so this is urgent, hence the Agenda+. While 1.23% is high, this change would only affect a (likely small) subset of cases and presumably we can easily measure how big the subset is (though that would delay things further). It's not intractable to add a use counter that measures how frequently `light-dark()` color values are used via inheritance — the tradeoff being that by the time we have data on this, the number will be higher. ---- @tabatkins @bramus Just wanted to make sure you saw https://github.com/w3c/csswg-drafts/issues/13836#issuecomment-4443629547 because it explains in great detail how the problem spans _way_ more widely than design tokens, or even custom properties as a whole. But also that when it comes to custom properties, mixins will make it way, way worse because then there is no way to work around it. This is a huge footgun when it comes to composable design systems, and renders `color-scheme` effectively unusable in practice for anything other than the root element unless you literally use no dependencies you don't control and no external components. The only reason this problem hasn't surfaced as a pain point yet is that these features are not used widely yet. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13836#issuecomment-4460365287 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 May 2026 13:58:43 UTC