Using Dexie prevents the browser from enabling the bfcache because of the usage of BroadcastChannel about dexie.js HOT 4 CLOSED

Here is a github issue that relates between bfcache and BroadcastChannel whatwg/html#7253

from dexie.js.

Thanks for sharing this information which wasn't something I was aware of. The issue seems to be broader than just BroadcastChannel - the indexedDB connection itself would prevent bfcache according to https://web.dev/bfcache/#always-close-open-connections-before-the-user-navigates-away

I suppose a correct solution would be to listen to the pagehide and pageshow events to take down BroadcastChannel and IDBConnections and bring them up again in the pageshow event if I understood the article correctly.

I suppose this would be doable but it would have to be done carefully in a prerelase at some point.

from dexie.js.

I'm running into this exact problem as well. Firefox, Chrome, and Edge all will ignore the bfcache, because of the registered listeners. However, it appears Safari doesn't behave this way and will still attempt to load the page from the bfcache regardless. The IndexedDB just ends up being in a corrupt state. Would be nice to opt into using the Service Worker implementation via configuration or have some sort of logic implemented to handle this.

from dexie.js.

Solved in [email protected] by subscribing to pagehide/pageshow and taking down BroadcastChannel and IDB connections. I've been able to verify that the BroadcastChannel isn't blocking the bfcache anymore.

from dexie.js.