web-platform-tests / web-platform-tests/wpt
web-animations/interfaces/AnimationEffectTiming/iterationStart.html should check value unchanged after TypeError
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6.2k
- Forks
- 3.9k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 586
Description
The last test in iterationStart.html tests that AnimationEffectTiming objects can't have a negative iterationStart assigned. The test should also assert that any previously set value is unchanged after the erroneous assignment.
Likewise for other AnimationEffectTiming objects with restricted inputs.
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 web-animations/interfaces/AnimationEffectTiming/iterationStart.html, especially its last test for assigning a negative iterationStart. Verify that the existing value remains unchanged after the assignment throws a TypeError, then review other AnimationEffectTiming tests with restricted inputs for the same missing check. Done means the relevant tests cover both the error and preservation of the prior value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100