- From: Nolan Lawson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Sep 2021 16:57:39 +0000
- To: public-css-archive@w3.org
Thank you for the clarification. It wasn't clear to me from reading the spec that scopes are recursive. If they are, then that solves "recursive donuts" quite nicely! As for the second point you raise, I agree that option 2 would allow for `.red p` to work. This is actually what I meant by "crossing the lower boundary," i.e. the `.red` is in the donut, and the `p` is in the donut hole inside the donut (there is a lower boundary between the two). I think if option 2 were in the spec, then frameworks like Vue and Svelte would have a smoother upgrade path to `@scope`. I'm not even sure they could emulate their current `.red p` behavior without that change. (Unless they identify and parse descendant selectors and generate new selectors based on those, e.g. `.red:scope p:scope`… Possible, but messy.) -- GitHub Notification of comment by nolanlawson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6574#issuecomment-912678576 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 September 2021 16:57:41 UTC