Skip to content

Selector specificity cannot be reliably represented as a number #1042

Open
@JakeQZ

Description

@JakeQZ

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions