WPT
wpt / IndexedDB / idb-explicit-commit.any.html
Spec: Indexed DB ↗
Runs: Chrome 155.0.8039.0 (wpt@6ec9fd59f, 2026-09-03) | Firefox 157.0a1 (wpt@6ec9fd59f, 2026-09-03) | Safari 251 preview (wpt@5ce815a83, 2026-08-27) | Ladybird 1.0-795e1 (wpt@7e3d005d7, 2026-09-03) | Servo Servo 0.6 (wpt@09159dcb3, 2026-09-02) | Blitz 188486089 (wpt@a95401e4e, 2026-09-02)
View on the Blitz WPT dashboard | Open test on wpt.live | wpt.fyi
| Chrome | Firefox | Safari | Ladybird | Servo | Blitz | |
|---|---|---|---|---|---|---|
| Total | 12/12 | 12/12 | 12/12 | 12/12 | 11/12 | NOT RUN |
| Subtest | Chrome | Firefox | Safari | Ladybird | Servo | Blitz |
|---|---|---|---|---|---|---|
| Explicitly committed data can be read back out. | PASS | PASS | PASS | PASS | PASS | — |
| commit() on a version change transaction does not cause errors. | PASS | PASS | PASS | PASS | PASS | — |
| A committed transaction becomes inactive immediately. | PASS | PASS | PASS | PASS | PASS | — |
| A committed transaction is inactive in future request callbacks. | PASS | PASS | PASS | PASS | PASS | — |
| Puts issued after commit are not fulfilled. | PASS | PASS | PASS | PASS | PASS | — |
| Calling commit on an aborted transaction throws. | PASS | PASS | PASS | PASS | PASS | — |
| Calling commit on a committed transaction throws. | PASS | PASS | PASS | PASS | PASS | — |
| Calling abort on a committed transaction throws and does not prevent persisting the data. | PASS | PASS | PASS | PASS | PASS | — |
| Calling txn.commit() when txn is inactive should throw. | PASS | PASS | PASS | PASS | PASS | — |
| Transactions with same scope should stay in program order, even if one calls commit. | PASS | PASS | PASS | PASS | PASS | — |
| Transactions that explicitly commit and have errors should abort. | PASS | PASS | PASS | PASS | FAIL | — |
| Transactions that handle all errors properly should behave as expected when an explicit commit is called in an onerror handler. | PASS | PASS | PASS | PASS | PASS | — |