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

From: Joshua Bell <notifications@github.com>
Date: Tue, 17 May 2022 11:51:49 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/381/1129206972@github.com>

> If this is the case, [the spec here about IDB version change](https://w3c.github.io/IndexedDB/#open-a-database) should change to say something like “If the page is not active but salvageable, do not send the versionchange event, but the page should be marked as unsalvageable”.

SGTM

But I agree with dmurph re: outstanding transactions. 

I'm the only active spec editor here (any volunteers?); PRs welcome to help address this!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/381#issuecomment-1129206972

You are receiving this because you are subscribed to this thread.

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

Received on Tuesday, 17 May 2022 18:52:00 UTC