Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201)

While I'm still checking (looks good so far), I did have the following concern/question... It is admittedly a concern about a missing test rather than spec issue, but I also wanted to confirm what the testing behavior would be if it existed...

`idbtransaction-objectStore-finished.html`, and `idbobjectstore-index-finished.html` cover the expected `InvalidStateError` throwing immediately after an `abort` (and suggest by their test names that "finished" at least definitively occurs within `abort`). However, I don't see any tests for an `abort` throwing immediately after another `abort` (as would be consistent with this understanding (of one subset) of "finished" since `abort` is to throw upon a transaction being "finished"). (FWIW, besides my manual checking, my regex to check the files was `abort\([\s\S]*abort\(`.) Should there be such a test which checks for `InvalidStateError` immediately after a prior `abort`?

-- 
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/pull/201#issuecomment-300973033