TPAC 2023 status report

[inexorabletash]

See also:

• 338

• 364

• 389

Progress in the last 12 months

In the spec itself, only editorial changes have been made in the last 12 months. These include:

• 395

• 398

• 401

• 409

• 404

• 407

• 411

• ... plus a handful of Bikeshed syntax updates, typos/grammar fixes, etc.

The set of new APIs (relative to 2.0) remains unchanged:

• databases() - implemented in Chromium and WebKit, but not Gecko
• durability - implemented in Chromium and WebKit, but not Gecko
• request - implemented in Chromium, WebKit and Gecko
• commit() - implemented in Chromium, WebKit and Gecko

No new PRs that haven't merged.

New unresolved issues since last TPAC:

• 402 - process

• 403 - feature request; a great idea, but unlikely w/o strong consensus with both library authors and implementers

• 412 - unspecified behavior

Moving to CR/Rec

Relevant:

• 402

See comments there, namely: we'll need to be more rigorous about getting consensus before landing any normative changes. But the change rate is low.

I believe these are the highest priority issues to tackle:

• Normative changes/corrections:

  • 412 - some discussion, needs PR, tests, and implementer commitment to align

  • 381 - some discussion, needs PR, tests, and surveying implementations to see if we're aligned

  • 375 - has a PR and tests, just needs implementer commitment to align

• Cross-spec integration

  • 400

  • 391

  • 334

There are plenty of other ways the spec could be made more rigorous tracked as issues, but they would just be editorial. PRs welcome!

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

Bit of a broken record here, but additional editors would be helpful. @aliams stepped down as editor leaving just @inexorabletash. Reviews for editorial-type changes can get done by the community, but actively pushing workstreams forward would strongly benefit from other implementers stepping up to help as editors.

cc: @marcoscaceres @LJWatson @siusin

[inexorabletash]

Note that I won't be attending TPAC 2023 in person, and the timing is pretty bad for the spec status reports session, so I'm not planning to participate live. I'm not expecting much discussion about IndexedDB, but thanks in advance for capturing any conversation in the minutes.

Extra big thanks to all the people that volunteer to be editors. :wink: