- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Sep 2021 17:50:19 +0000
- To: public-css-archive@w3.org
> This does raise a slightly different issue that I think we need to clarify. It might be a mistake for the spec to say that :scope is prepended as an ancestor to scoped selectors, unless otherwise used in the selector. The difference being: The right way to handle this is to just say that selectors within a @scope block are [scoped](https://drafts.csswg.org/selectors/#scoping) to the elements matched by the upper-boundary selector (plus the additional restriction that they don't match things past a lower-boundary selector). No need to talk about modifying any selectors; the scoping concept does what we need already and with greater functionality, since you can, if needed, match earlier parts of the selector to elements outside of the scope (or prevent that, by explicitly using `:scope` in your selector). ---- Tangent: we might want to fold the lower-boundary concept into the definition of "scoped" so you don't need to do any hacking of the existing concept. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6574#issuecomment-912707610 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 17:50:21 UTC