"construct a ReadableStream object" doesn't specify the realm
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.3k
- Forks
- 403
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 4
Description
This algorithm is used inside the Fetch spec in https://fetch.spec.whatwg.org/#http-network-fetch, which has a request whose client is either an environment settings object that can provide the realm, or null. It's used outside of Fetch from at least https://w3c.github.io/ServiceWorker/#fetch-event-respondwith, which specifies the Service Worker's realm manually.
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 with the “construct a ReadableStream object” algorithm in the Fetch Standard and compare its use from HTTP-network-fetch with the Service Worker fetch-event respondWith algorithm. Confirm how each caller supplies or lacks a realm, then update the specification so the algorithm’s realm behavior is explicit and consistent in both contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100