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

Thanks @dmurph  for the feedback and @inexorabletash for the comment!
I didn't know about the problems with keeping the transactions complete (and its potential difficulty of implementation). So sounds like these are the way to go for now:

- Allow pages with IDB connection and keep track of the locked version, and evict when a database issues a request for a different version from the locked version
- Keep blocking pages with open IDB transactions from entering back/forward cache

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

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