service-manual 2 linked patterns checked
web.dev Create an offline fallback page
Documents custom offline fallback pages, service-worker cached offline pages, manual reconnect buttons, automatic online-event reload, server polling, and the need to provide users something controlled rather than a browser default failure.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Fallback path | Choose fallback path when the user needs an alternate way to finish the same task after the primary method is blocked, unsupported, unavailable, or unsuitable. | The fallback path is a different route to the same user outcome or an explicitly named support handoff, not another attempt at the same failing operation. | web.dev documents controlled fallback pages with manual reconnect rather than a browser default failure. |
| Offline state | Choose offline state when connection loss changes what users can read, edit, save, submit, refresh, upload, export, or share. | The offline indicator appears only when connectivity affects the current task or a global app capability users can reasonably act on. | web.dev supports cached offline fallback pages, manual reconnect, automatic reload on online events, and server polling. |
Comparisons supported by this source
- Fallback path vs retry vs error state vs service unavailable page
web.dev documents controlled fallback pages with user-facing reconnect behavior rather than browser default failure.
- Offline state vs error state vs loading spinner vs progress bar
web.dev supports cached offline fallback pages, manual reconnect, online-event reload, and server reachability polling.
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: web.dev. Last checked: .