Re: [w3c/manifest] Define how the manifest is fetched (#481)

> Chromium implementation doesn't use the same path as <link>, instead we use the <link> to get the cross origin and the src then we start a regular fetch when needed. 

We do the same in Gecko. 

> The manifest is loaded on demand and even though I do not exactly remember why I did not want to fire the events, it would make sense to not fire them if they could happen at any point between page load and page close (they become worthless and a great footgun).

Agree. We don't want developers to confuse the load or error events with meaning that it's being installed or cancelled. The UA is free to load the manifest resource as needed, when needed. 

---
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/481#issuecomment-237742499