HTML Class Token Difference
Subtract literal HTML class tokens while preserving surviving duplicates and order; CSS selector syntax and case folding are not applied.
Description
Subtract literal HTML class tokens while preserving surviving duplicates and order; CSS selector syntax and case folding are not applied.
Removing literal class names differs from applying a CSS selector. This operation subtracts matching tokens while retaining the order and repeats of survivors.
When to use this tool
Subtract literal HTML class tokens while preserving surviving duplicates and order; CSS selector syntax and case folding are not applied.
- Prepare the supplied classes, remove fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter classes, remove. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.classes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Split classes and remove on HTML ASCII whitespace. Filter every classes token whose exact value occurs in remove, then join survivors with one space.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| classes | classes. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| remove | remove. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.classes | The classes value under the stated formula or text convention. |
{
"input": {
"classes": "a b a c",
"remove": "b c"
},
"output": {
"result": {
"classes": "a a"
}
}
} Limitations and assumptions
- No CSS escape processing, selector matching or case folding is applied. Duplicate surviving classes remain duplicated.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
For actual document behavior, inspect a parsed DOM and the relevant HTML algorithm. These tools transform supplied tokens, observations or coordinates; compare the browser result when parsing or layout matters.
References
Similar or alternative tools
- HTML Class Token Duplicate Audit
Audit class token duplicates using HTML ASCII whitespace splitting and exact case-sensitive token identity; does not parse selectors or CSS escapes.
- HTML Class Token Stable Merge
Merge explicit HTML class attribute strings as stable exact token union after ASCII whitespace tokenization; preserve first token appearance.