As I understand it, Open Web App manifests used by Gecko currently have to be served from the same origin as the app.
There is a discussion at the W3C about whether the standardised version of web app manifests should have this same restriction. I would encourage you to contribute to that discussion if you have strong feelings either way http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0635.html On Tue, Jun 3, 2014 at 11:59 PM, Austin King <[email protected]> wrote: > Howdy, > Working with a partner, the question came up: > > > I'd like to move the manifest to our CDN to avoid this, but it looks like > the manifest format > > requires the same-origin for the manifest[1]. Our CDN serves static files > with the access- > > control-allow-origin header–do you know if the manifest supports this, by > any chance? > > > > [1]: > https://developer.mozilla.org/en-US/Apps/Build/Manifest#Serving_manifests"; > > Also, my response: > > > My first thought is that changing the URL of an manifest, changes the > identity of the > > application. Users will have to re-install and will have two apps on > their homescreen. > > > > At least this would be true for Firefox for Android." > > Can anyone answer the first question or add to my answer? > > thanks, > ozten > _______________________________________________ > dev-webapps mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-webapps > _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
