Re: [w3c/IndexedDB] TPAC 2022 status report (Issue #389)

For reference:

TPAC 2020 #337 
TPAC 2021 #364

# 2022 Status Report

## Progress in the last 12 months

Same as last time, unfortunately - extremely limited progress. 

Normative changes:
* #383 

Editorial updates:
* #384
* #387 
* #388

Implementer updates:

* Chromium focus has been on third party storage partitioning, prototyping storage buckets, and file system access handles, so not much work has happened with Indexed DB specifically. No additional prototyping on new methods has been done since last year.
* Safari 15 supports IDBCursor.prototype.request, IDBTransaction.prototype.commit(), IDBTransaction.prototype.durability, IDBTransactionOptions durability member. This means all the new v3 members are now supported in all 3 engines. 
    *  TODO: update the 🚧 ...new in this edition. It is supported in ... 🚧 banners!

Active PRs:

* #386 (for #375)
* #334 

Expected near future work:

* Integration with Storage Buckets
* #381 

## Moving to CR/Rec

* FPWD #348 from last year. Progress!
* As noted last year, the actual normative deltas since V2 are fairly minimal. That said, they're now adopted by all 3 engines, so publishing a V3 as soon as possible makes sense.
* However, the big needs for the spec are around integration with other specification infrastructure. Until these are sorted out, it feels inappropriate to move forward. They are:
   * Back/forward cache
   * Storage endpoints
   * Storage buckets

## What is your plan to unblock it and do you need any help?

* Active editors from other implementors would be of significant benefit.
    * Even simple issues like #386 are stalled without being able to get input from other browsers. 
    * Brainstorming on #334 in particular would be welcome, and my hope is to discuss next steps with anyone interested at TPAC.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/389#issuecomment-1207092681

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/389/1207092681@github.com>