respondWith is not implementable as written
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
https://w3c.github.io/ServiceWorker/v1/#fetch-event-respondwith step 10.3.1.2.5.1 calls https://fetch.spec.whatwg.org/#concept-get-reader which calls https://streams.spec.whatwg.org/#acquire-readable-stream-reader
This last expects to be called in the usual ES way, with a current Realm and whatnot. But the above-cited step is running "in parallel", and hence has no current Realm.
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
Read Service Worker fetch-event respondWith step 10.3.1.2.5.1 and follow its references into the Fetch and Streams specifications. Determine how the cited reader acquisition can operate while the step runs in parallel without a current Realm; the issue is done when the specification inconsistency has a documented resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100