Description
Pair explicit transition properties with cyclic duration/delay lists; no shorthand parsing, timing interpolation or special all/none expansion.
CSS combines token syntax, property-specific value rules and layout/cascade processing. These are separate layers: splitting a declaration does not establish that its value is valid, and arithmetic on resolved lengths does not perform browser layout. Each tool here handles an explicit numeric representation or a stated lexical subset.
Pair explicit transition properties with cyclic duration/delay lists; no shorthand parsing, timing interpolation or special all/none expansion.
When to use this tool
Use this tool to pair explicit transition properties with cyclic duration/delay lists; no shorthand parsing, timing interpolation or special all/none expansion.
How to use the tool and how it works
- Enter properties, durations, delays using the input definitions below.
- Run the operation. Resolve malformed-input errors before interpreting the result.
- Read result.slots. Interpret signs, units, ordering and null values using the rules below.
Require nonempty duration and delay lists and nonnegative durations. For each supplied property index j, pair durations[j modulo durationCount] and delays[j modulo delayCount].1, 2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| properties | Supplied transition-property names in slot order. | Dense list of at most 128 strings, each at most 8,192 UTF-16 code units. |
| durations | Nonempty nonnegative durations in one common time unit. | Dense list of at most 128 finite numbers, subject to the stated integer/shape rules. |
| delays | Nonempty signed delays in the same time unit as durations. | Dense list of at most 128 finite numbers, subject to the stated integer/shape rules. |
| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.slots | Input-order name/duration/delay records after independent list cycling. |
{
"input": {
"properties": [
"a",
"b",
"c"
],
"durations": [
1,
2
],
"delays": [
0
]
},
"output": {
"result": {
"slots": [
{
"name": "a",
"duration": 1,
"delay": 0
},
{
"name": "b",
"duration": 2,
"delay": 0
},
{
"name": "c",
"duration": 1,
"delay": 0
}
]
}
}
}Limitations and assumptions
- Use consistent time units. Negative delays are retained; all/none and shorthand strings are not expanded or interpreted.
- Lengths and times must already be resolved to consistent numeric units. Lexical helpers intentionally support smaller grammars than a full browser CSS parser; malformed supported-subset input causes an error.
- Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.
Alternative or Complementary methods
Use a full CSS parser or browser style/layout APIs when escape handling, error recovery, computed styles or the full cascade matter. These tools expose focused transformations and audits of supplied data.
References
Similar or alternative tools
- CSS Animation List Slot Pairing
Pair explicit animation names with cyclic duration/delay lists; no shorthand parsing, timing interpolation or special all/none expansion.
- CSS Custom Property Name Token Audit
Audit a deliberately restricted ASCII custom-property token grammar -- followed by letters/digits/underscore/dash; not full CSS identifier validation.