Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)

dmurph left a comment (w3c/manifest#1171)

My main thoughts here are:
- On Chrome, we download through the document, which can hit things like the service worker, and also shows up in things like the devools network panel
- I hesitate to open up the options here for another user agent to download the icons in a different way, as this reduces consistency here between platforms.
- Normal image fetches from a document get a bunch of things like headers, which might be used by the server to, say, customize the image based on the user's profile, whether they are in an experiment group, etc. Maybe can't fetch unless auth headers are there?

It's hard to know how important keeping this consistent, if there is a requirement out there someone would have here. I think my biggest concern would just be consistency.

HOWEVER - I think also we have an effort to decouple the manifest parsing from the document. There are a lot of benefits there too, allowing services to cache data about a manifest & the icons for distribution. But - yeah - not sure what the right answer is here.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1171#issuecomment-2845946326
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1171/c2845946326@github.com>