Re: [w3c/IndexedDB] How should IDB connections and outstanding IDB transactions behave when a page enters back/forward cache? (Issue #381)

Reading your comment again - apologies - you already mentioned this behavior :)

Adding @inexorabletash  - perhaps you know who to route this to for spec changes.

My intuition would say:
- We still want to abort outstanding transactions, and I'm tempted to say that the page should be 'unsalvageable' in this case, as otherwise we are introducing an edge case for developers that they probably don't handle well (all transactions could be aborted at any time & they would need to recover).
- We can't really keep them operating / open due to the locks they hold.
  - Well, we COULD do this but they we would want to mark the page as unsalvageable if any other connection was opened or txn attempted to start on the same object stores. Pretty hard to implement.



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

Message ID: <w3c/IndexedDB/issues/381/1129000777@github.com>