Join GitHub today
consider how Client API should behave with bfcache #1038
In Firefox we have a back-forward cache (bfcache). When in effect you get
How should we handle the
My current plan is:
On Chrome, we do not have a bfcache.
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.
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 with other UAs?