Re: [w3c/IndexedDB] Steps for committing a transaction don't prevent the cleanup steps from allowing subsequent requests (Issue #489)

Zaggy1024 left a comment (w3c/IndexedDB#489)

Semi-related, it seems like Firefox, Chromium and Safari all automatically commit a transaction if the cleanup stage is reached and no requests have been made. All I see mentioned in the spec is this:

> The implementation must attempt to commit an [inactive](https://w3c.github.io/IndexedDB/#transaction-inactive) transaction when all [requests](https://w3c.github.io/IndexedDB/#request) placed against the transaction have completed and their returned results handled, no new requests have been placed against the transaction, and the transaction has not been [aborted](https://w3c.github.io/IndexedDB/#transaction-abort)

It seems like this should be an explicit step during cleanup, since that's the only place where it makes sense to detect that it should be committed.

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

Message ID: <w3c/IndexedDB/issues/489/3994928473@github.com>