Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668)

Another point: the most compelling reason we identified yesterday (I believe @dmurph raised) is privacy-sensitive: when performing these "automated" installs without user supervision (e.g., installing from sync, admin policy or a default app installed by the user agent), there is a privacy issue in sending a request to the server of every app being installed.

If we can install from a manifest without loading a whole document, it allows us to have the manifest body - and its icons - be the thing distributed (e.g. over sync) rather than its URL, and install it offline without hitting the server. (Unfortunately, this won't allow us to have a service worker cached, without [Web Bundles](https://web.dev/web-bundles/, but at least we can have the app icon registered with the system.)

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

Message ID: <w3c/manifest/issues/668/1397843580@github.com>

Received on Friday, 20 January 2023 02:15:17 UTC