improve specificity calculation #129
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| }; | ||
|
|
||
| node.nodes.forEach((child) => { | ||
| const itemSpecificity = selectorSpecificity(child); |
There was a problem hiding this comment.
This is why I was mentioning extracting since I've been seeing this
There was a problem hiding this comment.
Yes, each time I copy/paste a bit I remind myself that I should fine a way to have these imported from a central util bundle :D
Antonio-Laguna
approved these changes
Jan 6, 2022
I want it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://drafts.csswg.org/selectors/#specificity-rules
I misread this as being the sum, it is not.
It has to be the most specific.
In practice it being wrong will rarely lead to a different result.
So not prio for release