Re: [w3c/manifest] Define core web manifest to enable extensions (#471)

Will take a look! thanks for the pointer. Please be warned that you shouldn't mess with how to obtain a manifest, as it's carefully designed to work with the security model of the Web (i.e., it's not just JSON you can just grab.... CORS and CSP play a role, and there are a bunch of security restrictions, etc. that it took a long time to work through). That's why the manifest spec only allows you to add and process simple values, but doesn't let you interface with how to obtain a manifest or other moving parts. 

Regarding the API, it's all to do with the lifecycle of the web application - you could generate the icons on the fly, for instance. I've done that before using a Service Worker. We don't have much of an idea of what an API might look like yet... I've opened #472 to discuss.  


---
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/471#issuecomment-227997939