Shadow DOM Handling
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
This is a placeholder issue which will closely mimic the outcome of https://github.com/w3c/element-timing/issues/3 (at some point it may even be merged if the upstream issue fixes both)
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 by reading this repository's Shadow DOM handling and compare the intended outcome with the linked w3c/element-timing issue #3. Define the required behavior from that upstream issue before identifying the relevant specification sections; done means the container-timing behavior matches the agreed upstream resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100