- From: DarkWiiPlayer via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Mar 2023 08:18:26 +0000
- To: public-css-archive@w3.org
I think this solves a different issue than `(.content > *)` lower boundary. One is useful for including the intended lower boundary in the scoped rules like any other element, so a `p.lower-boundary` would have any scoped styles for `p` applied, but not any nested `p` elements. `:scope-end` would provide a more explicit way of selecting only the lower boundary, regardless of what rule it matches. There might also be cases where we might want to combine them by having `(.lower > *)` as our boundary and selecting `:has(> :scope-end)` to get to the "inclusive" lower boundary instead of what CSS would consider the actual boundary. -- GitHub Notification of comment by DarkWiiPlayer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8617#issuecomment-1484707417 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 March 2023 08:18:27 UTC