Re: [w3c/IndexedDB] Can a "committing" transaction be aborted? (Issue #437)

For the former:

* The step about _"If this's state is committing or finished, then throw an "InvalidStateError" DOMException."_ we may have included the "committing" restriction because once a transaction has started committing then calling `abort()` may not successfully abort the transaction; the front-end has told the back-end to go ahead, so whether or not the abort() succeeds depends on whether the back-end sees the request before the commit completes. I don't recall with certainty.
* Regarding _"A transaction can be aborted at any time..."_ isn't describing the restriction on `abort()`, but that an abort could happen for any time for all sorts of reasons e.g. the back-end detects an I/O error and gives up.
* Re: Chromium implementation - unclear if that was intentional deviation from the spec or not. :(

Feedback from other implementers welcome!

For the latter, see https://infra.spec.whatwg.org/#algorithm-control-flow - agreed that "Otherwise" is redundant in this case.






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

Message ID: <w3c/IndexedDB/issues/437/2581315974@github.com>