A route is more than a rendered component. It has a URL that may be bookmarked, an entry in browser history, a focus target, a scroll position, and a data snapshot. A client router can change one of those while accidentally leaving the others behind. Browser back and forward may restore a suspended page without a fresh request. Speculative loading can help a likely next step, yet it can also consume bandwidth or request private data too early. The case-review queue supplies one consistent workflow for testing those boundaries.
Topics in this track
- URL State and History Entry Contracts — Put shareable state in the URL and choose push or replace according to user intent.
- Back-Forward Cache and Restored State — Recheck volatile or private data when a suspended page resumes from browser history.
- Route Scroll and Focus Restoration — Restore reading position and keyboard context after client-side navigation and delayed content.
- Navigation Prefetch and Private Data Budget — Warm likely next routes without preloading private content or starving current work.
Prerequisite paths
Browser Routing and History State; React Effects and Request Races; Accessible forms: connect labels, errors, and focus.
Neighbor track
HTTP Delivery and Cache Ownership.
Practice path
Build Project: history-safe review journey and check decisions in Web Development: navigation and delivery decisions quiz.