FetchObserver (for a single fetch)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.3k
- Forks
- 403
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 4
Description
In https://github.com/whatwg/fetch/issues/447#issuecomment-281731850 @jakearchibald sketched some APIs based on @stuartpb's work which @bakulf then implemented:
- https://developer.mozilla.org/en-US/docs/Web/API/FetchObserver
- https://dxr.mozilla.org/mozilla-central/source/dom/webidl/FetchObserver.webidl
- https://dxr.mozilla.org/mozilla-central/source/dom/webidl/Request.webidl#59
That issue got closed after we landed a subset of that API in Fetch (you can finally abort a fetch). Let's discuss the remainder here (though not priorities, that's #436).
cc @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 with the linked Fetch issue comment and review FetchObserver.webidl and Request.webidl referenced in the issue. Determine which parts of the previously sketched single-fetch observer API remain outside the landed abort subset; this issue is done only when the remaining scope and specification changes are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100