- From: Bramus via GitHub <noreply@w3.org>
- Date: Fri, 15 May 2026 13:47:47 +0000
- To: public-css-archive@w3.org
+1 to what Tab said here. I believe we need to find the answer in that direction. Maybe by this third state Tab proposes, or maybe by extending the custom property registration to indicate what _stage_ of the value computation gets inherited (specified/computed/used + normal for the current situation). That would allow distinguising between is it the `light-dark()` or is it the fully resolved color that gets inheritd? Or is it the em-value or the computed px value you get? Etc. This is also something @kizu brought up on the call, and also something that was brought up in different issues in this repo (or maybe at the houdini/fxtf repo) before. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13836#issuecomment-4460288269 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:47:47 UTC