Carefully audit all uses of "in parallel" in the spec
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
I'm only partway through respondWith, and there's all sorts of things in there that should not be happening "in parallel", and other parts of this spec have similar issues (e.g hthttps://w3c.github.io/ServiceWorker/v1/#dom-cache-put does mutations on a shared data structure "in parallel"; it's not clear how that's supposed to work exactly).
Please audit all uses of "in parallel" to ensure they actually make sense.
@domenic @wanderview
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 reviewing the "in parallel" usage in respondWith and the Cache.put section at https://w3c.github.io/ServiceWorker/v1/#dom-cache-put, then search the rest of the Service Worker specification for the same wording. Done means every use has been audited and any wording that does not make sense for shared mutations or other operations has been identified for correction.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100