Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)

diekus left a comment (w3c/manifest#1191)

Just double checked this. It is indeed a reproduceable behaviour that happens on Chromium (Edge/Chrome) on Windows/macOS and Safari on macOS.

The app's frame shows some UX to specify that a connection is needed, and to an extent this is by design as wiping out the cache does clear all the data from the origin, and this indeed provide subpar UX for web apps. 

@marcoscaceres iirc Safari saves web apps independently from the origin and sandboxed, but cache should still affect them? 

There might be a good first run/hydrate discussion in here. Tagging with feature request atm while I dig a bit more.


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

Message ID: <w3c/manifest/issues/1191/3457384063@github.com>