Koncem srpna Ian Hickson začal diskusi:
It seems like we are talking about the following kinds of scenarios:
1. User goes to a page, then, without closing the page, goes offline and uses it, then goes back online and continues to use it. The page and its subresources are always at their most up-to-date. Interactions with the page while offline are synced to
the server when going online.
2. User goes to a page, then closes the browser. User restarts the browser while offline, and goes to the page. User restarts the browser again while online, and goes to the page. The page and its subresources are always at their most up-to-date. Interactions with the page while offline are synced to the server when going online.
3. Same as 1 or 2, except that the user is not online for long enough to fully download the updated resources. The application doesn't stop working, it is still usable the second time the user is offline.
My proposal is that we add a new attribute to the <html> element, which flags that the page is a Web app that wants to be pinned for offline execution and that when you next fetch the file or one of its subresources while online, it should try to update all the subresources atomically.Nejedná se o kopii ani jedné ze stávající implementací, více se blíží Google Gears.
Hixie specifikaci zatím psát nezačal, nad podobou specifikace se stále diskutuje, pokud vás zajímá, přočtěte si vlákno Offline Web Apps v mailing listu WHATWG.