- From: Joshua Bell <notifications@github.com>
- Date: Thu, 20 Apr 2017 11:31:26 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 20 April 2017 18:31:59 UTC
Spec has: > Let transaction be the upgrade transaction associated with database. If one does not exist or it is finished, throw an "InvalidStateError" DOMException. But in this case, a TransactionInactiveError is thrown instead in Chrome/Firefox and asserted as such in tests: ```js tx.abort(); db.createObjectStore('s'); // throws TransactionInactiveError ``` Noted by the ever vigilant @brettz9 over in https://github.com/w3c/web-platform-tests/issues/5612 but it's the spec that's wrong here since impls/tests match. Unfortunately, the "finished" notion for transactions is a bit squishy. Spec-wise we may be able to just drop the "or it is finished" bit from these methods and then tidy up the transaction lifecycle at some point in the future. -- 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/192
Received on Thursday, 20 April 2017 18:31:59 UTC