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)

I forgot to note an important part of this issue: The reason why the second put succeeds (in our implementation at least) is because the steps to fire a success event also resets the transaction state to active if it is inactive. Since the cleanup is in a microtask checkpoint, it managed to set the state to inactive before the request could try to fire a success event, so by the time the success fires, the transaction thinks it's ready to go again.

I have a feeling that we _should_ be able to assert that the cleanup steps never act on a transaction that is not in the active state. However, aborting also needs to clear the cleanup event loop for that to be the case.

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

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