The future of routing with the Navigation API
summary
Argues that the Navigation API replaces the old History API with concrete features: a navigate() function that returns a promise, a cancellable navigate event that lets code intercept and delay navigations, and per-navigation finished/commit promises plus traversal and stable entry IDs. Demonstrates interception showing the browser tab spinner with one real server request, explains state vs transient info, notes current browser support needs Chrome flags and Firefox/Safari work in progress, and calls out new helpers like pattern matching.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 7:50Hash routing to Navigation API
- 11:23History API limitations
- 16:13History API design problems
- 18:01Navigation API features
- 24:46Intercepting navigations
- 30:17History entries and state
- 34:30Developer benefits
- 36:36Browser support and outlook
- 40:45Closing remarks and Q&A
related talks
39mSailing Uncharted Waters: Exploring the New Navigation API
31mModern Front End Routing
17mModern Routing
47mFlutter Navigation 2.0 in Real Life
26mVue-router and its techniques
21mNavigation in Flutter - the not-so-obvious parts
05mLightning talk from Eric Vlad Vicenti
49mNavigation Component, feedback from the trench