WPT: attribute and node removal scenarios
Open
Nobody has claimed this yet.
WPT
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
We've updated the spec to deal with the containertiming attribute being removed and the node itself being removed from the DOM, but there are no WPT tests for this, we should track the updating of the test suite to cover this scenario
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
No specific test file is named. Start by locating the existing WPT tests for the containertiming attribute and read the updated specification linked in the issue. Add coverage for removing the attribute and removing the node from the DOM, then run the relevant WPT tests to confirm both scenarios pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- testing, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100