Offline
summary
Proposal and prototype for an in-browser proxy called Service Worker gives sites programmatic control of fetch events, a JS-driven cache API and the ability to respondWith synthetic responses, aiming to make offline shells that mediate content instead of brittle AppCache pages. Chrome and Firefox have prototypes; persistent storage still relies on the Quota API and user consent, captive portals and background sync remain unresolved, and no universal sync API exists yet so conflict resolution and eviction policies fall to each app.
AI-written summary · about
chapters (14)
- 0:00Offline panel intro
- 1:27Service Worker APIs evolution
- 6:24Remote content assumptions problem
- 12:29Offline data model and app shell
- 16:01Service Worker design implications
- 18:56Storage persistence and intent
- 26:48Network state detection
- 32:26Offline data limits and subscriptions
- 36:23Installable app permissions
- 44:15Web apps in app stores
- 50:38Third-party APIs in offline
- 53:45Synchronizing offline data
- 56:58Offline data security
- 59:28Summary and future
