- From: Joshua Bell <notifications@github.com>
- Date: Wed, 06 Oct 2021 14:55:53 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/IndexedDB/issues/364/937216821@github.com>
Oops, past the deadline for specification status report. Here we go... # Specification Status Report - TPAC 2021 ## Progress in the last 12 months Extremely limited progress. Implementers appear to be focusing elsewhere (e.g. [Storage Foundation](https://github.com/WICG/storage-foundation-api-explainer) and [Access Handles](https://github.com/WICG/file-system-access/blob/main/AccessHandle.md)). Google Chrome does plan to invest more in Indexed DB performance in 2022, and plans to explore if new indexing-related functionality could help developers migrate APIs Normative changes: * Correct assertion that a transaction's scope is a "set of object stores" that is "fixed for the lifetime of that transaction", which is not true for upgrade transactions. Editorial updates: * Use sorting definitions from [infra](https://infra.spec.whatwg.org/) * Textual simplifications, e.g. drop "running" from algorithm invocation Implementer updates: * Safari 14 supports `databases()` Updated discussion / issues: * Renewed interest in support for boolean keys #76 * At TPAC 2019 we discussed `putAll()` for batch population of stores. * Initial implementation experiments in Chrome showed no meaningful performance improvement, although we don't have high confidence in the results and would welcome other implementer feedback. #69 * Following Chrome's pause of work on putAll(), there was more discussion about pre-filling stores with JSON #224 * More support expressed for a `closed` property on database connections. #333 * More discussion about explicit control over transaction lifetimes #34 * Requests for editorial changes - _PRs welcome!_ * Rename "array key" to "composite key" (filed by the editor)? #360 * Clarify that consistency model is strict serializability #355 * Clarify that IDBTransaction.onerror fires when errors bubble up from requests #353 * Clarify queueing behavior when opening a database #354 Miscellaneous: * Migrated from Travis-CI to GitHub Actions ## Moving to CR? * Need to go to FPWD first. #268 - I think we've all been busy. * Set of normative changes since v2 is still fairly minimal [revision history](https://w3c.github.io/IndexedDB/#revision-history) ## See also * 2020 update #338 * 2019 update #290 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/364#issuecomment-937216821
Received on Wednesday, 6 October 2021 21:56:05 UTC