Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)

Are you suggesting the SW shouldn't update after each navigate? If so, I disagree. If I shipped a SW that served broken pages, users would be stuck with it for 24 hours? We added the 24hr max-age limit because the longer the max-age, the more trouble you're getting yourself into.

If you're saying that we should perform an update after a fetch event if it's >24hr since an update, even if the fetch is for a subresource, then yeah, that makes sense.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/814#issuecomment-173586216