Estimated reading time : 4 min · Published
Define a useful scope
Classify tasks such as reading stable information, preparing a draft, checking availability or paying. The latter depend on data and confirmations that should not be assumed current offline. Explain unavailable actions usefully.
A simple site can remain useful through lightweight pages and reliable links without adding an offline application. Assess actual interruptions and essential content first. Additional mechanisms need owners and tests rather than merely technical names.
Describe states unambiguously
Separate local draft, awaiting transmission, server receipt and completed processing. Write a message and recovery action for each. A connection icon or disabled button alone does not explain what happened to the request.
MDN documents service workers and offline or background operation. Assess availability and lifecycle in the project’s target browsers. Browsers may interrupt work, so the journey should remain understandable without relying on continuous execution.
Test interruption at an inconvenient moment
In a test environment, disconnect before sending, during transfer and after server receipt. Restore the network and reload. Check what is retained, lost, repeated or shown as complete. The difficult case is often uncertainty about an already-received request.
Use a new session and another device if cross-device continuity is promised. Ask someone unfamiliar with the architecture to test messages. They should understand the remaining action and how to avoid placing a second order.
Fictional exercise: a form shows a draft and then a pending submission. Disconnect after server receipt but before confirmation returns. The interface can no longer infer whether another submission would duplicate the request. Provide a “receipt needs checking” state and an authorised lookup by test reference before offering to repeat it.
navigator.onLine is a connectivity hint, not proof that the site’s API responds. Likewise, a fulfilled fetch() promise does not mean the HTTP status indicates success; check status, response content and the agreed business state. A draft stored on one device is neither a received request nor a backup available on another device.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Observed moment or response | State to explain to the visitor | Recovery check |
|---|---|---|
| Disconnected before any submission | Local draft only | Do not announce server receipt. |
| Server received it, confirmation lost | Receipt needs checking | Look up the test reference before resubmitting. |
| 422 from the demonstration API | Data needs correction under the test contract | Explain the error without inventing success. |
| navigator.onLine is true, API unavailable | Service unconfirmed despite the network hint | Offer understandable recovery without blind submission. |
- MDN · Using Fetch
MDN describes navigator.onLine limitations and response handling with Fetch. Sources consulted on 22 October 2026. States and the 422 code belong to a fictional test contract.
- MDN · Navigator.onLine
Read the mechanism and its limits in this primary reference.
Check freshness and privacy
For retained information, show date and permitted use. Old availability may orient a visitor without authorising a booking. Define what remains on the device after logout and who reviews shared-device risks.
After a new release, check resource replacement and local-data compatibility. Provide a way to recover permitted drafts or restore simple operation. Deliver states, interruption tests, retention rules and degraded-mode limitations.
Primary documentation : MDN : Offline and background operation.
Reference documents
- MDN : Offline and background operation · Source consulted
Further reading
For teams relying on the website daily, this guide extends journey checks with connectivity, telephony and continuity considerations. It helps frame workstation and network needs; actual offer conditions still need checking with the relevant provider.
Connexion Internet France : business connectivity guide (French)
Content updated on
