- From: Jake Archibald <notifications@github.com>
- Date: Thu, 15 Jan 2015 05:01:27 -0800
- To: w3c/manifest <manifest@noreply.github.com>
Received on Thursday, 15 January 2015 13:01:54 UTC
@benfrancis > https://evernote.com/ might not register the Service Worker, but https://evernote.com/Home.action would Why would you want to offer ServiceWorker features to home-screen-launched but not browser visited? > Another use case I just thought of is that when a user uninstalls the app from their operating system, the service_worker property could perhaps also be used to unregister the Service Worker. That doesn't feel right if the browser & home-screen-thing share storage and SW. I wouldn't expect removing a home screen icon to remove features I previously had in the browser, maybe even features that were registered in the browser. If the home-screen-thing has a different storage & SW, the system can detect which origins the user has icons for and remove storage & SW without the manifest. > calling home to measure install metrics How would you tell the difference between a normal SW install, and one triggered from add-to-homescreen? --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/161#issuecomment-70082236
Received on Thursday, 15 January 2015 13:01:54 UTC