New logic to detect PWA offline support
summary
Chrome changes the install logic so the browser actually sends a fake HTTP request to the manifest start_url in a sandbox with no network and only shows the PWA install prompt if the service worker returns 200 status code for that request. The old check treated any fetch handler, even an empty one that triggers the dinosaur offline page, as sufficient. Experiments run behind check-offline-capability flag in Chrome 88, warning mode in 89, then full enforcement after a grace period.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:28Installed PWA on desktop
- 3:06Install prompts on mobile
- 3:18Install prompts on desktop
- 3:33PWA with a Service Worker
- 3:55What is supposed to happen if offline?
- 4:16Requirements for installable PWA
- 5:09Logic to detect PWA offline support New
- 7:10Timeline
- 8:11Call to action
- 8:32Chrome Dev Summit 2020
related talks
26mBehind the Scenes of a Sevice Worker
14m5 tips for your PWA
44mKeynote: Uncovering the secrets of Progressive Web Apps
17mTransforming your Web Application into a PWA - Why and How?
44mPWA - Welcome to the Future
48mPWAs, are we there yet?!
41mOffline Web Apps don't exist anymore!
52mOffline web applications don't exist anymore!