Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Selector specificity cannot be reliably represented as a number #1042

Open
JakeQZ opened this issue Mar 1, 2025 · 0 comments
Open

Selector specificity cannot be reliably represented as a number #1042

JakeQZ opened this issue Mar 1, 2025 · 0 comments
Labels
bug
Milestone
10.0.0: Clean up ...

Comments

@JakeQZ
Copy link
Contributor

JakeQZ commented Mar 1, 2025

It's an ordering mechanism.

MDN suggests putting the values into a three-colum vector.

Selector::getSpecificity() may fail to give the correct ordering if there are 10 or more of the same kind - which, admittedly, is unlikely.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
10.0.0: Clean up things, rework the API
Development

No branches or pull requests
1 participant
@JakeQZ