Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87)

> "If the active flag of the transaction is unset after a single success event, then wouldn't it become impossible for more than a single request to be sent in a transaction?"

That is covered in https://w3c.github.io/IndexedDB/#fire-success-event and https://w3c.github.io/IndexedDB/#fire-error-event - the transaction is active while the event is being dispatched. Therefore another request can be made, and when that request completes the event will fire, once again setting the transaction to active.

> ...where requests should still be allowed to continue before deactivation: when an error event is fired but the event is canceled

What do you mean by "continue" here?  If you mean that further requests should be allowed, then yes - again, that's allowed during dispatch because the transaction is set to active.

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