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

Just a note to say that I would strongly support this change.

I'm currently [working on](https://github.com/krellian/kiosk) a use case for web app manifests, similar to the app store use case, where a web app is installed onto a digital signage display remotely.

In this case the digital signage runtime may not have a traditional browsing context from which the user can install a web application, it instead provides a remote API whereby an administrator can install a single web app to the display, which loads in a single application context.

This use case would be made much simpler if the manifest could be processed directly from its own manifest URL, rather than assuming an app is installed by a user agent fetching a manifest via a link relation in a separate document loaded in a browsing context.

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