You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warns when a selector uses a pseudo-class or pseudo-element name that doesn't exist in the CSS specifications (e.g. a typo like :hoverr or ::befor) — an unknown pseudo-class/element causes the entire selector (and rule) to be silently dropped by browsers.
What type of rule is this?
Warns about a potential problem
Example code
/* WARNING: 'hoverr' and 'befor' are typos, not real pseudo-classes/pseudo-elements */a:hoverr {
color: red;
}
p::befor {
content:"";
}
/* OK */a:hover {
color: red;
}
p::before {
content:"";
}
I assumed no-unmatchable-selectors already covered this, based on its name. After checking the implementation, it only handles :nth-*() selectors with impossible AnPlusB values — it doesn't validate whether a pseudo-class/pseudo-element name actually exists. Hence this proposal.
Activity
BHyeonKim commentedon Sep 1, 2026
I assumed
no-unmatchable-selectorsalready covered this, based on its name. After checking the implementation, it only handles:nth-*()selectors with impossibleAnPlusBvalues — it doesn't validate whether a pseudo-class/pseudo-element name actually exists. Hence this proposal.nzakas commentedon Oct 20, 2026
Sounds good to me. Marking as accepted. 👍