- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2023 20:09:47 +0000
- To: public-css-archive@w3.org
The other way to exclude the scope is just `* > ...`, right? And when nesting you can just do `> ...`, which might be simple enough to be worth leaving it as the way to handle things. Note that the host element is *unmatchable* except by the `:host` pseudo; it's not contextual in the selector itself. That is, you can't write `:host.foo` - by definition the `.foo` won't match the host element. I suspect that it'll be relatively common to want to match additional selectors against the scope, tho. For host elements we allow that with a functional form - `:host(.foo)`, but we don't (yet?) have a `:scope()` functional form. I lean weakly towards "no change", then. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8377#issuecomment-1409264178 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 January 2023 20:09:49 UTC