- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Mon, 18 Apr 2016 05:07:30 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/454/211351532@github.com>
> A dev can already fetch() their manifest, so what would this provide and why? There seems to be an assumption in a lot of the spec that a user that has the manifest installed will never visit the app other than via the new icon on their homescreen. My reading of @felquis comment on https://github.com/w3c/manifest/issues/417#issuecomment-168700461 was that he has users hitting URLs that are part of the app but have landed there directly from links on the web. He then needs to decide if he should encourage them to install the app or not but has no way of knowing if they already have. Two use cases/questions: 1. How does a dev know if the user has installed the manifest (and when) so they can try to force an update if necessary or encourage the user to perform the install? 1. How does the dev know which manifest the user agent has interpreted as the current manifest (if any) if the user lands on a page that is inside the scope of multiple possibly previously-installed manifest? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/454#issuecomment-211351532
Received on Monday, 18 April 2016 12:08:03 UTC