- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Apr 2024 18:02:08 +0000
- To: public-css-archive@w3.org
> We need to fix this issue, ASAP. +1, if we're going to do this, we should not wait any longer. > I am looking at the pages on the use counter (I assume you're talking about the old use-counter?) Anyway, as previously stated, I added more advanced use-counters a while back, and it’s been in Chrome Stable for a few weeks now. - [CSSBareDeclarationShift](https://chromestatus.com/metrics/feature/timeline/popularity/4783) (0.00029%), which triggers when retaining interleaving/trailing declarations in their place (by way of a wrapping `@nest` rule) would make a difference to the result of the cascade. (Yes @kizu, this counter does the right thing in the cases you mentioned). - [CSSNestedGroupRuleSpecificity](https://chromestatus.com/metrics/feature/timeline/popularity/4784) (0.00017%), which triggers when `@nest`-wrapping bare declarations within a nested group rule would make a difference to the cascade. Making this move would allow nesting e.g. `@media` in pseudo-element rules, which doesn't work currently since we're wrapping in an `&`-rule. These numbers are small, and I’m pretty confident that Blink API Owners will approve this change in Chrome, provided that we act quickly, and have clear willingness from Mozilla and Apple to actually carry out the change (@emilio, @fantasai). The [previous meeting notes](https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1969468715) suggests that we're waiting for use counter data. I think we can consider this unblocked now. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-2048158814 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 April 2024 18:02:08 UTC