Pseudo-Class State Targets Table
Supported pseudo-class state semantics; does not compute matching state from selector text. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Pseudo-classes select elements under defined states or conditions.
Pseudo-classes select elements under defined states or conditions.1
A stored state explanation does not query a document or inspect actual interaction. Use Pseudo-Class State Targets Table to look up a supported term.
When to use Pseudo-Class State Targets Table
Use Pseudo-Class State Targets Table to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use Pseudo-Class State Targets Table and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Pseudo class using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| pseudoClass | Pseudo class | string | Required; constraints below |
Enter one of the exact supported pseudoClass tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| hover | element designated by pointer hover |
| active | element being activated |
| focus | element has input focus |
| focus-visible | focused element when UA determines focus indication should be visible |
| checked | selected radio, checkbox or option state |
| disabled | supported element disabled by document semantics |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"pseudoClass": "focus-visible"
},
"output": {
"meaning": "focused element when UA determines focus indication should be visible"
}
}Limitations and assumptions
A stored state explanation does not query a document or inspect actual interaction. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use Utility-First Class Classifier Note for a related task: Utility classification requires a defined registry of independently recognized class tokens.
Use Attribute Selector case Flag [i] Lookup for a related task: Attribute equality can use explicit case-sensitive or ASCII-insensitive comparison.
References
-
Pseudo-Class State Targets Table — tool.io
Similar or alternative tools
- Utility-First Class Classifier Note
Utility classification requires a defined registry of independently recognized class tokens.
- Attribute Selector case Flag [i] Lookup
Attribute equality can use explicit case-sensitive or ASCII-insensitive comparison.