IndexedDB: Complete Failures

Completely failed files: 357; Completely failed subtests: 11; Failure level: 11/1151 (0.96%)

Test Files

  1. /IndexedDB/idb-explicit-commit.any.html (9/9, 100.00%, 0.78% of total)
  2. /IndexedDB/idbobjectstore_createIndex15-autoincrement.htm (1/2, 50.00%, 0.09% of total)
  3. /IndexedDB/idb-explicit-commit-throw.any.html (1/1, 100.00%, 0.09% of total)
Test Show/Hide MessagesCh73
/IndexedDB/idb-explicit-commit.any.html (9/9, 100.00%, 0.78% of total)OK
A committed transaction becomes inactive immediately.FAIL
A committed transaction is inactive in future request callbacks.FAIL
Calling abort on a committed transaction throws and does not prevent persisting the data.FAIL
Calling commit on a committed transaction throws.FAIL
Calling commit on an aborted transaction throws.FAIL
Calling txn.commit() when txn is inactive should throw.FAIL
Explicitly committed data can be read back out.FAIL
Puts issued after commit are not fulfilled.FAIL
commit() on a version change transaction does not cause errors.FAIL
/IndexedDB/idbobjectstore_createIndex15-autoincrement.htm (1/2, 50.00%, 0.09% of total)OK
Auto-Increment Primary KeyFAIL
/IndexedDB/idb-explicit-commit-throw.any.html (1/1, 100.00%, 0.09% of total)OK
Any errors in callbacks that run after an explicit commit will not stop the commit from being processed.FAIL