On 16 June 2015 at 00:59, Jonas Sicking <[email protected]> wrote: > One thing that is tricky is that in the new manifest spec the manifest > URL is meaningless. In order to update an icon we need to re-download > the HTML file and see what manifest URL it points to. > > This is especially problematic if the user "pinned the website" rather > than "pinned the page", i.e. if we bookmarked the start_url rather > than the current page URL. What do we do if the page on the start_url > doesn't link to a manifest? Or links to a different manifest? Does the > spec address this? >
My understanding is that the spec assumes that the manifest URL does not change, including when stored on a CDN. It says that the user agent may "periodically check if the contents of a manifest has been modified (e.g., by honoring HTTP cache directives associated with the manifest or by checking for updates after the web application has been launched)". You do need to keep a record of the URL of the document the app was installed from (or at least its origin), in order to check that any future start_url or scope are on the same origin as that document, because these are steps you need to take when processing any new or updated manifest. There are quite a lot of assumptions here though so I have filed an issue to ask for clarification https://github.com/w3c/manifest/issues/384
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
