service-manual 1 linked patterns checked
web.dev: Back/forward cache
Documents browser back/forward cache behavior and recommends avoiding unload handlers and adding beforeunload listeners only when necessary, such as while unsaved user changes are present.
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 |
|---|---|---|---|
| Exit warning | Choose exit warning when departure has already been attempted and leaving would lose work or context that is not safely recoverable. | The warning appears only after a departure attempt or immediately before a known session boundary that could cause loss. | web.dev documents browser navigation-cache considerations and recommends limiting unload-related handlers. |
Comparisons supported by this source
- Exit warning vs autosave form vs draft state vs confirmation dialog
web.dev documents the browser-cache cost of unload handling and recommends using beforeunload only when necessary.
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: .