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

marcoscaceres left a comment (w3c/manifest#1191)

I still think this sounds like an implementation bugs, but it's good that it's been identified. We need to evaluate if it's developer error or not also. Caches get invalidated no matter what, and when that happens the start URL should just be run to rebuild/reconfigure everything. 

So, unless I'm not getting something, I'm not sure if this needs spec text... I guess we could add a note that user agents should be away of this, if it's affected both Chrome and Safari. 

What do folks think? 

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

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