Re: [w3c/ServiceWorker] consider how Client API should behave with bfcache (#1038)

On Chrome, we do not have a bfcache.
Instead we do a navigation but with a special [Load-Preferring-Cache](https://docs.google.com/document/d/1o8KImLPrJQcMNqvd_a-1V8fEVgtVeEJww453ZQ1hGuo/edit#heading=h.nak275rb0o40) flag which lets Chrome re-use assets in the HTTP cache regardless of staleness (with [a few exceptions](https://docs.google.com/document/d/1o8KImLPrJQcMNqvd_a-1V8fEVgtVeEJww453ZQ1hGuo/edit#heading=h.n0bogtd49pq3)). This behavior is also used for the Tab Restore flow.

With a Service Worker involved, we think it would be best to allow the developers to identify which user journey is playing out and decide for themselves if they want to fallback to the default behavior or use a custom behavior on a per resource request basis.

I'm currently trying to piece out a solution from the current SW/Fetch specs.
Will report back soon.

Side-note: if this use case is reasonable and can (has to) be done in Chrome, then should developers be able to override bfcache and control the user experience via their service worker?

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