W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

[IndexedDB] Spec Status Update

From: Joshua Bell <jsbell@google.com>
Date: Tue, 20 Oct 2015 11:06:32 -0700
Message-ID: <CAD649j5QcXa8czVA2ExcfDD635n8KWs_qEmGLO92W=OiyrPJeg@mail.gmail.com>
To: "public-webapps@w3.org" <public-webapps@w3.org>, Ali Alabbas <alia@microsoft.com>, Arthur Barstow <art.barstow@gmail.com>
A quick pre-TPAC update on the status of Indexed DB for the Web Platform WG:

The "first edition" of Indexed DB[1] became a W3C Recommendation in January
2015. Since then, the editors (Joshua Bell from Google and Ali Alabbas from
Microsoft) have started work on a "second edition" [2] Editor's Draft. The
work so far has been incremental and following the "edit then review" model
favored by the working group. To summarize the work so far:

* Spec moved to GitHub [3]
* Feature request wiki migrated to GitHub issue tracker [4]
* Moved to ReSpec "contiguous IDL" and various respec fixes
* Spec overhauled to describe methods in imperative/procedural form
* ECMAScript binding cases for keys and keypaths not covered by Web IDL
specified explicitly
* Several new attributes, methods and events already shipping in Gecko
and/or Blink have been documented:
  * event on IDBDatabase for abnormal close
  * getAll and getAllKeys methods on IDBObjectStore and IDBIndex
  * objectStoreNames attribute on IDBTransaction
  * openKeyCursor on IDBObjectStore
  * test cases for these have been submitted to web-platform-tests
* In addition, some more aspirational changes that have not shipped yet in
any implementations have been specified based on feature requests,
including binary keys, renaming stores/indexes and a handful of other
methods.
* There is current discussion (mailing list, github, ...) for some some of
the most popular but also more substantial requests, including a
Promise-friendly extension to the API and an observer API

Feedback is appreciated and welcome, especially in these areas:
* Overall review to ensure that the "imperative" rework of the spec did not
introduce behavior changes
* Intentional behavior additions to the spec (called out as "☘ new in this
edition ☘")
* Review of the tracked issues [4] - comments, clarifications, indications
of support or disagreement, or just plain bikeshedding
* In particular, comments on the Promises proposal[5] would be helpful, as
we're trying to introduce minimal changes to avoid forking the API

[1] First Edition TR: http://www.w3.org/TR/IndexedDB/
[2] Second Edition ED: https://w3c.github.io/IndexedDB/
[3] GitHub repo: https://github.com/w3c/IndexedDB/
[4] Issue tracker: https://github.com/w3c/IndexedDB/issues/
[5] Promises proposal: https://github.com/inexorabletash/indexeddb-promises
Received on Tuesday, 20 October 2015 18:07:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:58 UTC