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

You don't need a document to install an app though. Case in point: we have app stores that index an app based on its manifest URL (also enterprise admins can request the installation of an app by specifying its manifest URL).

While you can't register a service worker without loading a document, you can absolutely download icons, register an app with the OS, and prepare it for launching, without downloading any documents. The purpose of this work is that therefore user agents shouldn't be _required_ to modify their interpretation of the app based on the (possibly nonexistent) document URL.

There are two scenarios:

- Installation from a document. Document URL is available, but there could be any number of documents that link the same app.
- Installation without a document, e.g., from an app store. There is no document URL.

In either of these scenarios, the installed app should be the same. Also, I don't want Document X and Document Y to link the same manifest, but result in a different app experience.

The spec currently doesn't actually allow the second scenario at all, so it doesn't reflect reality.

-- 
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/668#issuecomment-794849467