Re: [w3c/manifest] Introduce window.Application global object instead of manifest.webmanifest (#769)

I spent two days to find an elegant way to read the manifest content without fetch it by js code over the browser.

I’m agree with you, loading webmanifest as an external resource is not elegant but still better than writing our app settings in js libraries or in a small js file, or even write it as inline code directly in the page.
I know the webmanifest spec still is unstable, but not in general. almost all the modern browsers has implemented this feature.

I tried the method you’ve used in your app, a couple of months ago and it didn’t work.
At least we have to have a link tag with rel=“manifest” in head, then we can set href attribute dynamically. but still not elegant.



-- 
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/769#issuecomment-513459029