- From: Joshua Bell <notifications@github.com>
- Date: Wed, 18 May 2022 08:34:10 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 18 May 2022 15:34:22 UTC
As @dmurph outlined above, an open transaction is observable from other contexts and requires code to be running on the page and responding to events to either keep the transaction alive or allow the transaction to complete. I think those are contrary to the intentions of BFCache, per the principles, _"anything that happens while the document is not fully active should be treated as if it never happened"_ (so a transaction shouldn't commit) and _"The document must not retain exclusive access to shared resources"_ (so it shouldn't be observable) > If some browser were to allow the page to go into BFCache and out again, why would we want that to be out of spec? In that case, we'd want to spec/align on that behavior where it's observably different, right? So we need a proposal detailing that behavior. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/381#issuecomment-1130175027 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/issues/381/1130175027@github.com>
Received on Wednesday, 18 May 2022 15:34:22 UTC