- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Apr 2024 07:53:36 +0000
- To: public-css-archive@w3.org
> I actually think the IACVT idea might be the lowest hanging fruit You didn't say "free", but I'd still like to clarify that we will not get this behavior for free just by having groups. `@group` would need to behave like a mini-`@layer`, and we'd basically need `revert-group`. But it's certainly not impossible, and we can definitely explore it. I can investigate more if it becomes clear that we want to go down this path. > Yes, that's exactly what we did to CSSStyleRule, and that's vastly more used. This is exactly what we _didn't do_ in Chrome, because we have no way of proving that the change is safe. Also, this is the only part of CSS Nesting WPT coverage that was excluded from the Interop 2024 focus area, because we have no path towards actually making the change. I still support "useful `@group`" as a path forwards, but ideally we'd get `CSSRule` vs `CSSGroupingRule` right from the start. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2080405904 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 April 2024 07:53:37 UTC