Recovering from start failures
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Currently when a service worker fails to start, the result is a network error. A service worker failing to start can happen due to a bad script or other non-transient errors, so it would be more useful for the user to have a fallback that bypasses the service worker in this case.
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
No source file, test, or entry point is identified in the issue. Start by reading the issue and its seven-comment discussion to determine the intended fallback semantics and where the Service Worker specification should define them; done means an agreed, testable behavior for start failures rather than a network error.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100