[w3c/manifest] Clarify how image objects should be fetched (#443)

Chrome stable has this bug - https://sw-cors-demo.herokuapp.com/

1. Image would be requested
1. SW would cache the request & response
1. "Add to homescreen" pressed
1. Icon would fail to load

This is because the icon was fetch with mode "cors", and the service worker responded with an opaque response.

Chrome has since fixed this issue, but this spec should detail how images should be fetched to avoid other UAs making the same mistake.

Fetching should be similar to https://html.spec.whatwg.org/multipage/embedded-content.html#update-the-image-data - as in mode "no-cors".

---
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/443