← back to v145 · indexeddb-sqlite-backend-in-memory-contexts

conformance · v145

v145 · indexeddb-sqlite-backend-in-memory-contexts — conformance probe

5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.

browser: spec: https://www.w3.org/TR/IndexedDB/ chromestatus: #5126896685809664 generated 2026-06-01T08:14:32Z by conformance-author-v1-subagent
0
pass
0
fail
0
blocked
5
total
id contract kind verdict detail
indexeddb-exposed indexedDB is exposed on the global — the backend rewrite to SQLite preserves the same Web API surface. exists
indexed-db-factory-open-is-function indexedDB.open is a function — the canonical entry point for database creation that the new backend serves. typeof
idb-object-store-put-exists IDBObjectStore.prototype.put exists — write API behaviour is unchanged by the SQLite backend. typeof
idb-transaction-prototype-commit IDBTransaction.prototype.commit exists — explicit commit semantics are supported by the new backend. typeof
idb-open-roundtrip Opening and closing a database round-trips — exercises the backend without observing any web-facing change. script