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

benfrancis left a comment (w3c/manifest#1171)

I tend to agree that icon/image fetching should be possible outside of the document the manifest was linked from. There could be all kinds of architecture designs for how to install an application where the functions of downloading, caching and updating icons are delegated to browser chrome or the underlying operating system. In Firefox OS for example I believe at least at one point icons were initially fetched by browser/system chrome to provide a preview but then stored (in IndexedDB) and displayed by the separate homescreen application after installation.

In general anything that helps decouple app installation from the document is a good thing from my point of view.

An edge case I can imagine that could create a problem is if fetching an image resource requires some form of authentication like a cookie being set, but there all kinds of reasons why I think that should be discouraged.

FWIW in WebThings Shell we currently fetch icons from system chrome rather than the document, but there's still work to do there around caching and updating images.

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

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