In a page utilizing Indexed DB, what should the expected behavior be for an
IDBTransaction created during the window.onunload event callback?
e.g.
window.onunload = function () {
var transaction = db.transaction('my-store', IDBTransaction.READ_WRITE);
transaction.onabort = function () { conso
On Tue, Feb 21, 2012 at 1:40 PM, Joshua Bell wrote:
> In a page utilizing Indexed DB, what should the expected behavior be for
> an IDBTransaction created during the window.onunload event callback?
>
> e.g.
>
> window.onunload = function () {
> var transaction = db.transaction('my-store', IDBTr
I'm not sure we should include this in the IDB spec. The reason is that I
would expect every browser to provide different guarantees based on their
internals. In our case after the Javascript engine finishes its processing,
the server starts its processing and once started the server started i
The whole issue of "what happens if the user leaves the page while
there are running transactions" is something that we've left up to
implementations. IIRC this was debated a long time ago but the
conclusion was basically that implementations will use different
strategies for dealing with this. Bas
