- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Dec 2022 14:51:51 +0000
- To: public-css-archive@w3.org
> > A compound selector preceding a pseudo-compound selector is excluded from the definition of the latter. > > div::before::marker:hover is not defined, only ::before:hover. > > I'm not sure where you're getting that from. `div::before::marker:hover` is definitely allowed by the grammar (both now that I've provided `<complex-unit>`, and before when it was just expanded in-place). > > The prose definition did make mention of it being preceded by a compound selector, explicitly, which I've fixed as part of another edit. Now it correctly mentions that it can be preceded by a compound or pseudo-compound selector. `<complex-selector-unit>` and the changes in the prose were exactly what I was hoping for. I am bit late, but thank you for all these edits. If you allow me a last comment, I feel like defining `:is()` as taking `<forgiving-selector-list>` is a bit over-generalized because its argument is highly context-sensitive, as noted in your addition to the introduction of *4. Logical Combinations*. > The logical combination pseudo-classes are allowed anywhere that any other pseudo-classes are allowed, but pass any restrictions to their arguments. (For example, if only compound selectors are allowed, then only compound selectors are valid within an `:is()`.) Maybe something like *Unless otherwise specified for the context, `:is()` is a functional pseudo-class taking a `<forgiving-selector-list>` as its sole argument* would be more helpfull. Same thing for `:not()`. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7085#issuecomment-1353215226 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 December 2022 14:51:53 UTC