Re: [manifest] How does updating work? (#384)

> but they are using it correctly. The declaration of using a manifest is independent of its content and the URL (hence it should be possible to update the manifest if the URL changes). 

This will not work.

An app can be installed from any page of the app. How is the user agent meant to know that some new manifest URL it comes across corresponds to the same app as an already installed manifest? Different pages on the same origin could point to different manifests corresponding to different apps.

If I install a Google Maps app from a page at:

https://www.google.com/maps/place/The+Warfield/@37.782739,-122.410156,18z/data=!3m1!4b1!4m2!3m1!1s0x80858085a9d7abdb:0x70d2c0624acc91fa

which links to a manifest URL at

https://www.google.com/maps/manifest.webmanifest

how will I get updates for that manifest?

If the user then navigates to 

https://www.google.com/calendar/render?pli=1#main_7

on the same origin which links to a manifest at

https://www.google.com/calendar/manifest.webmanifest

do I just assume that this new manifest URL replaces the old manifest, or do I have to wait for the user to navigate to the exact page they visited before at

https://www.google.com/maps/place/The+Warfield/@37.782739,-122.410156,18z/data=!3m1!4b1!4m2!3m1!1s0x80858085a9d7abdb:0x70d2c0624acc91fa

in order to update the Google Maps icon?

Good URLs do not change for a reason.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/384#issuecomment-119558987

Received on Wednesday, 8 July 2015 12:32:20 UTC