The HTML5 History API: PushState or bust!
summary
Explains how the HTML5 History API actually works: pushState takes a state object, title and URL but does not load a new page, and the browser fires a popstate event for back/forward navigation; warns against stuffing large HTML into the state (about 1KB practical limit) and recommends using localStorage for caching. Covers browser support gaps (IE arriving in 10) and shows a working car-search demo that updates filters, pushes URLs for sharing, and restores UI on back/forward.
AI-written summary · about
chapters (6)
related talks
40mpushState to the Future: Progressive Enhancement Using HTML 5 pushState
31mModern Front End Routing
30mThe State of HTML5 - Inaugural Address
33mPitfalls and Opportunities of Single Page Applications
39mSailing Uncharted Waters: Exploring the New Navigation API
43mIlluminating Horror Stories from the Browser API Haunted House
29mHTML5 JavaScript APIs
41mThe future of routing with the Navigation API
