Recovering from fetch failures
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
If your SW is buggy, or something changes in a particular browser that causes it to start throwing errors, the user gets nothing until you fix your SW (unless the browser provides a "retry without service worker" feature).
It'd be nice to allow the developer to recover in these cases
In many cases, a .catch() at the end of the respondWith promise lets them do that, but not in the case of a response that fetch deems unacceptable, eg an opaque response to a CORS request.
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 issue's description of Service Worker fetch failures, respondWith promises, and opaque CORS responses. Define the recovery behavior that should be exposed to developers, then determine how it fits the Service Worker fetch processing model and how completion would be tested.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100