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

@mgiuca 

> Installation without a document, e.g., from an app store. There is no document URL.
> The spec currently doesn't actually allow the second scenario at all, so it doesn't reflect reality.

The reality is a document is required to install an app. Sure, you can INDEX an app (it's name, icons, etc) but to me that is not INSTALLING an app.

The installation of an app requires a document. It often requires a service worker, fetching of js, css, caching off pages, numerous other stages during the install lifecyle of the service worker.

To really separate the document from the installation process - wouldn't the manifest file need to link to all the assets needed to install the app? i.e. is this issue trying to help address packaging of an app, and once packaged not really "needing" a document any longer? It seems to me the fact remains a document is needed to practically package and install an app. You could "index" it, but what does that really give you? You've indexed a bunch of icons, name, but not really done anything practical.

A document is an integral part of the manifest to describe where an app sits, how it can be accessed and installed? Maybe I'm misunderstanding the intention here though.

-- 
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-796972904