Re: [w3c/IndexedDB] TPAC 2026 Status Report (Issue #500)

SteveBeckerMSFT left a comment (w3c/IndexedDB#500)

## Progress (since TPAC 2025)

We have not made much progress on the actual spec text over the last 12 months.  With the Chromium implementation, we've been focused on reliability and performance improvements.  However, we can make progress now with TPAC 2026 happening.  Thank you to everyone who contributed PRs, issues, comments and WPTs in 2026.

### Last 12 months in review:

- [IndexedDB focus area](https://wpt.fyi/results/IndexedDB?label=experimental&label=master&aligned&view=interop&q=label%3Ainterop-2026-indexeddb) completed successfully with [getAllRecords()](https://w3c.github.io/IndexedDB/#dom-idbobjectstore-getallrecords) and [IDBGetAllOptions](https://w3c.github.io/IndexedDB/#dictdef-idbgetalloptions) implemented in Chromium, Firefox and Safari.
- [3 pull requests](https://github.com/w3c/IndexedDB/pulls?q=is%3Apr+state%3Aopen+created%3A%3E2025-11-01) created.
- [18 issues](https://github.com/w3c/IndexedDB/issues?q=is%3Aissue+state%3Aopen+created%3A%3E2025-11-01) created.
- [13 WPT](https://github.com/web-platform-tests/wpt/commits/master/IndexedDB?since=2025-11-01&until=2026-10-08) commits.

## Blockers

We plan to continue addressing developer feedback through additional IndexedDB API enhancements.  We should adopt the "living standards" model instead of creating another versioned spec like IndexedDB 3.0.  See #402.

## Testing

We continue to improve the [WPTs](https://github.com/web-platform-tests/wpt/tree/master/IndexedDB).  Verifying error handling remains challenging without automation to simulate out of disk space, file system errors and corruption.  See discussion in #431.

## Next steps

### Suggested [TPAC 2026 discussion topics](https://github.com/w3c/IndexedDB/issues?q=is%3Aissue+state%3Aopen+label%3ATPAC2026):
- Start modernizing the API with better promise support:
  - Maybe [Joshua Bell's proposal](https://github.com/inexorabletash/indexeddb-promises#transactions) from 10 years ago is a good starting point?
  - #34
- Consider new types of keys:   
  - #509 
  - #506
- Fix spec bugs in [getAllRecords()](https://w3c.github.io/IndexedDB/#dom-idbobjectstore-getallrecords):
  - #497 
  - #496
  - #494 

### Implementation backlog from prior TPACs
- Support more key types:
  - #492 
  - #76 
- Explore batched requests:
  - #376 
  - #69 
- Decrease transaction lifetime for special cases:
  -  #482
- Explore request priority or preload:
  -  #428
- Improve error handling:
  - #476

### What other topics would TPAC 2026 attendees like to discuss?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/500#issuecomment-6069915065
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/500/6069915065@github.com>