Add support for relative selector lists #75
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #74
This PR adds support for relative selectors used in
:has
while making the addition of other relative selector pseudo-classes in the future fairly simple.I added a new type
Relative
for this but I'm not sure whether or not this is the right design. The CSS spec states that, because:has()
takes a relative selector list, the arguments of:has()
are actually complex selectors. However, it seems a little odd to me to treat theleft
side of a complex selector asnull
(but that could be an alternate design), especially since the text talks about complex selectors being compound selectors separated by combinators. So the "first" compound selector would be nothing in the relative case — somehow feels wrong from the definition.Thoughts?