[web-animations-1] Clarify consequences of mis-sorted keyframes
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
There's a (non-normative) section of the spec that says
offset
...
Specifying an offset outside the range [0.0, 1.0] will cause a TypeError to be thrown.
Keyframes that specify an offset must be provided in increasing order of offset. Adjacent and equal offsets, however, are permitted.
If that MUST is violated, what happens? Would be good to say something here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the quoted non-normative offset section of the Web Animations Level 1 specification and inspect the surrounding keyframe-ordering requirements. Done means the specification clearly states the consequence of providing mis-sorted keyframes, with wording consistent with the applicable behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100