WICG / WICG/declarative-partial-updates
Zombie control by streamHTML
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 13
- Avg merge
- 12m
- Merged PRs (30d)
- 3
Description
The proposed method of declarative DOM updates is problematic in that it leaves the potential for many "zombie controllers" to be attached to the DOM at any given moment: each suspended on a promise but ready to start mutating the DOM again the moment the promise resolves.
What happens if a stream writer yields a promise that never resolves? Is that an unfixable memory leak?
What if many stream writers are attached to the same element -- can they get into a race condition with each other?
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
Review the streamHTML proposal and trace how suspended promise-backed controllers are attached to the DOM. Check the unresolved-promise and multiple-writers-on-one-element cases described here. Done requires an agreed behavior or design that addresses lifetime cleanup and race handling, documented in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100