- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2018 14:09:53 +0000
- To: public-css-archive@w3.org
It seems to me that since pseudo-elements were allowed to be effectively the subject [of pseudo-classing](https://drafts.csswg.org/selectors-4/#pseudo-element-states), we can't restrict the effect of pseudo-classing to "subsetting the _elements_ only" anymore. Yes, currently only pseudo-classes of user action are allowed for pseudo-elements, but I agree that @Loirooriol's example could be very useful in many cases. Maybe it would be useful to introduce something like "any pseudo-element" notation that would be combinable with pseudo-classes like `:mathches()`, `:not()` and probably `:is()` and would make the meaning of the selector unambiguous? E.g. something like `.somewhere .something::*:matches(::before, ::after):hover` (meaning that `:hover` belongs to the pseudo-element part, not the originating element)? -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2284#issuecomment-364122260 using your GitHub account
Received on Thursday, 8 February 2018 14:10:02 UTC