Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)

benfrancis left a comment (w3c/manifest#1171)

@marcoscaceres wrote:
> Checked implementations ahead of merging
> ...

Presumably this is during initial installation, but what about when updating?

Without the change in this PR it is my understanding that an OS could periodically directly fetch the icon of an already installed app from its icon URL to update an icon in an app launcher (e.g. in an app drawer/home screen/start menu/launchpad/dock) if it wanted to, outside of any browsing context. After this change it will always be necessary to wait for a browsing context to load a document linking to the manifest in order to download an updated icon. Do operating systems provide APIs for an installed web app (or the native browser app providing its application context) to update the icons of apps after installation?

I understand the points about CSP policies and the (slightly odd) use case of serving icons from a service worker, but it's kind of a shame to have to make this change because without it it's technically possible for a user agent to ask an OS to install a web app by just providing a manifest. After this change my understanding is the user agent will always have to fetch all of the linked image resources the OS might need itself and hand them over to the OS along with the manifest.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1171#issuecomment-4236188309
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1171/c4236188309@github.com>