[TASK] Deprecate greedy calculation of selector specificity#1022
Merged
Conversation
This constructor parameter is not used, and having the specificity calculation always done lazily is not a problem. This is the V8.x backport of #1018.
oliverklee
added this to the
8.8.0: Deprecate and replace some APIs, and a few fixes milestone
JakeQZ
approved these changes
Feb 27, 2025
Collaborator
I changed the commit message to "This constructor parameter will no longer be used", since it was being used. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This constructor parameter is not used, and having the specificity calculation always done lazily is not a problem.
This is the V8.x backport of #1018.