- From: James Atherton via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Aug 2020 11:25:44 +0000
- To: public-css-archive@w3.org
I'm not sure how specific `use-counter` can get but it should only count when the unset/inheritance happens and does not resolve to `initial` since libraries like https://propjockey.github.io/css-media-vars/ rely heavily on the IACVT fallback and has recently become popular - all the properties are set on :root so this specific modularity issue does not happen. Plus, others were at least experimenting with the previous chrome/firefox behavior too: https://twitter.com/gavinmcfarland/status/1289010777651847168 so use-counter would almost have to determine intention if it's just out there and now broken somewhere. --- Tangentially, If the change moves forward, the current-spec-behavior can be reproduced when https://github.com/w3c/csswg-drafts/issues/5325 is resolved by using `inherit` in the fallback. Which is a really good alternative. If the change doesn't move forward, there is no easy path alternative to reach the IACVT fallback in the nested/modular situation unless your new `validate` <a href="#issuecomment-665864719">#issuecomment-665864719</a> idea moves forward -- GitHub Notification of comment by James0x57 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5370#issuecomment-669870657 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 August 2020 11:25:46 UTC