- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Dec 2022 14:00:35 +0000
- To: public-css-archive@w3.org
I am sorry to disrupt your current discussion. If I correctly understand the reason for restricting `:host()` argument to `<compound-selector>`, I think these cases should also be invalid: - `:host(:host(.foo))` - `:host(:host-context(.foo))` - `:host(:nth-*-child(1 of .foo .bar))` - `:host(:current(.foo .bar))` - `:host(::part(part-name))` - `:host(::slotted(slot-name))` Basically, any functional pseudo-class/element taking a selector as its argument should be restricted to `<compound-selector>` (or any sub-production matching its argument syntax) and should disallow `:host()`, `:host-context()`, `::part()`, `::slotted()`. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7953#issuecomment-1367342598 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 December 2022 14:00:37 UTC