• New functionality
  • added transaction durability option, per discussion at TPAC 2019 #50
    • Supported in Chrome and Edge
• Other normative changes
  • remove File lastModifiedDate references, per discussion at TPAC 2019 #215
  • specify that read-only transactions can run in parallel but block a later read/write transaction from starting, and the read/write transactions similarly block later read/write and read-only transactions, matching implementations #253
  • disallow proxies as keys, matching implementations. #309
  • make transactions inactive during the value clone process, to prevent side effects (e.g. getters) from re-entering algorithms.
• Spec quality
  • Alignment with Infra and WebIDL syntax, term and convention updates.
  • Added Accessibility Concerns section #327

Pending changes:

• New functionality
  • (has PR) IDBObjectStore putAll() per TPAC 2019 discussion - Chrome has implementation experience, but no data ready to share yet.
  • (has PR) Manual commit per TPAC 2019 discussion - no implementation plans I'm aware of.
  • (has PR) IDBObjectStore / IDBIndex getAllEntries() per TPAC 2019 discussion - no implementation plans I'm aware of.
  • (has PR) IDBCursor close() per TPAC 2019 discussion - no implementation plans I'm aware of.
• Spec quality
  • (has PR) Define Indexed DB as a storage endpoint, per Storage, and integrate with "bottles" terms, etc.

Seems premature:

• Goals for V3 in charter state "The third edition adds new capabilities and improves developer ergonomics by using promises." KV-Storage as a Promise-based layer on top of Indexed DB has stalled. An alternative is to push on low-level support in Indexed DB (example) and encourage libraries to implement Promise support.
• Overall, new functionality since V2 is limited: see https://w3c.github.io/IndexedDB/#revision-history
  • databases() method #31, commit() method #234, request attribute #255, durability option #50

How to unblock:

• IMHO, at least one more "big" feature is needed (e.g. one of the above PRs) to justify the effort
• Need further implementation experience
• Any other interested editors? Both current editors are from Chromium-based browsers.
• Need a WD published at least.

• TPAC 2019 report