- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Oct 2022 00:15:15 +0000
- To: public-css-archive@w3.org
> - Con: first selector in a set of nested style rules has this special requirement, which is an odd positional requirement
I'm a bit concerned about the implications of this for editing of style sheets. In particular, it introduces cases where deleting a rule (which has the initial `&` to trigger the switch) will invalidate the rules after it, if they don't have that `&` trigger. For example, in the middle code block in [@tabatkins's comment](https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1268979633) deleting the `& li { margin: 0; padding: 0; }` rule will invalidate the rule following it.
Maybe it's something we can live with given all the constraints here, but I just wanted to point out explicitly what this implies about removing rules from style sheets in the process of editing them.
--
GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1269135501 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 October 2022 00:15:17 UTC