- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Nov 2022 14:55:41 +0000
- To: public-css-archive@w3.org
I may have misunderstood your resolution. Can you please clarify whether a pseudo-class that is not allowed to follow a pseudo-element should be invalid or should match nothing? Currently, it should be a user action otherwise it is invalid, and it matches nothing if the current action is not defined to follow the pseudo-element (or vice-versa). I also think to `::before:is(div :>> :hover)` or `::before:is(div **:hover)` assuming `:>` or `**` (cf. #7346, #4565) will ever be defined in Selectors 5, so my previous comment is definitely wrong. If the answer to my previous question is *it should be invalid*, can you clarify that logical combination pseudo-classes following a pseudo-element still accept a `<*-selector-list>`? Or I should just wait for your edits... -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7085#issuecomment-1328060337 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 26 November 2022 14:55:42 UTC