-
Notifications
You must be signed in to change notification settings - Fork 708
[selectors-4] Text of the "Compound selector" definition misses the Pseudo-elements part #5676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I guess this is basically the issue at the end of that section:
|
So |
No, they're complex selectors. The text is just written in a slightly ambiguous way, because precisely reflecting the grammar into English would be very fiddly and it's not necessary, since the grammar is the part that's normative. |
The text is still normative. It's fine if the text is looser than the grammar, but if it's stricter then it's adding additional constraints. So I would change to:
|
All right, ended up rewriting the complex selector section a bit, and tweaking pseudo-compound as well. |
…ector parts a bit. w3c#5676
Currently, the formal grammar of the Compound selector is
i.e. pseudo-elements (possibly pseudo-classed) can be part of Compound selector.
However, the definition of Compound selector in prose states that
and the formal grammar of the simple selector excluded pseudo-elements (since the resolution of #386). (As a side note, the current formal grammar seems to imply that the "bare" pseudo-element, like
::before
, technically falls under the Compound selector definition.)Shouldn't the text of the Compound selector definition be amended somehow to make it more clear that pseudo-elements also belong to it?
The text was updated successfully, but these errors were encountered: