service-manual 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.
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. |
Evidence Role
This source is treated as service-manual evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: web.dev. Last checked: .