Re: [w3c/IndexedDB] How should IDB connections and outstanding IDB transactions behave when a page enters back/forward cache? (Issue #381) from Daniel Murphy on 2022-05-17 (public-webapps-github@w3.org from May 2022)

From: Daniel Murphy <notifications@github.com>
Date: Tue, 17 May 2022 08:11:42 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/381/1128993089@github.com>

You could technically allow outstanding transactions if you let them 'complete' (allow JS to keep running until they committed), and paused any newly created transactions from starting.

problems:
- No guarantee that the txn will complete - in fact there was a common pattern of keeping a txn alive while some other task happened. could use this to keep JS executing on a tab
- complicated to implement - requires another state of pausing

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

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

Received on Tuesday, 17 May 2022 15:11:53 UTC