skip to content

Navigation and Page Lifecycle

3 roadmaps31 questions

You will learn how the browser moves between pages and states — history entries, URLs, back/forward cache, visibility transitions — and how SPA routers ride on top of it. Interviewers ask because every router bug and every lost-unsaved-work bug traces back here.

on this pageshow

explore

questions

page 2 of 2

Your web app's client-side routing is built directly on the History API. How would you decide whether to move it onto the Navigation API, and how would you sequence that change given uneven browser support?

level: principalimportance: nice to knowfreq 16%

basics

~20 s

Decide from what the current routing code costs you — bespoke click interception, focus and scroll bugs, no real transition lifecycle — against maintaining two engines while support is uneven. Sequence it behind one router interface, enable the new path progressively, and delete the fallback on telemetry.

open as a page

showing 31–31 of 31