[shared] rework compound pseudos priority logic #1474
Merged
+89
−28
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.
Context
This is an interim fix for #1473 to unblock some internal experiments. The larger bug requires a better solution at the API design level.
We currently enforce outer-key pseudo-elements, which by our sorting logic outputs
In the meantime, let's allow for compound selectors like
:hover::afterand sum up the priorities. We'll opt out of handling functional pseudo-classes (eg. :where(), :is(), :has()), as those don't follow additive specificities.This PR is a follow up to ca12618 to clean up failing signals and refine logic