Re: [csswg-drafts] [selectors-4]Why "Pseudo-elements cannot be represented by the matches-any pseudo-class"?

> It seems to me that since pseudo-elements were allowed to be effectively the subject of pseudo-classing, 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.

If I'm reading you correctly, I think you misunderstood what I meant by my previous comment. I'm not drawing any real distinction between elements and pseudo-elements; as far as Selectors is concerned, they're basically the same thing. (This is my entire point above; *because* a pseudo-element is effectively a new element, the pseudo-element selector is *not* equivalent in meaning to any other simple selector, and is instead basically a combinator into the "pseudo-children" of an element.)

> Maybe it would be useful to introduce something like "any pseudo-element" notation that would be combinable with pseudo-classes

I wouldn't mind recasting things a bit to add a real combinator into the "pseudo-children", where presumably the pseudo-element names are instead matched as tagnames, like `.foo :: before:hover`, or `.foo :: *:matches(before, after)`, etc.  I've looked into this before and there were some issues with parsing if we just reinterpreted `::` as a combinator; I'll have to dig up what they were, as I can't recall right now.

GitHub Notification of comment by tabatkins
Please view or discuss this issue at using your GitHub account

Received on Thursday, 8 February 2018 19:16:32 UTC