- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Nov 2024 10:44:30 +0000
- To: public-css-archive@w3.org
I’m with @benface here. It would feel inconstent when compared to other at-rules. I believe that the authors who are struggling with this right now are the ones that have used it before – [which not that many have](https://chromestatus.com/metrics/feature/timeline/popularity/4486). If they hadn’t seen/learned the old behavior, I think the current behavior caused by `CSSNestedDeclarations` is what they would have expected to happen in the first place _(which is also something Kevin mentions in his video: it’s regular cascade now)_. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11263#issuecomment-2507548301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 November 2024 10:44:32 UTC