Intent to Implement: IndexedDB v2: object store and index renaming

[Victor Costan]

Contact emails pwn...@chromium.org,jsbell@chromium.org Spec https://w3c.github.io/IndexedDB/ Summary In the IndexedDB 2.0 specification, the name attribute of IndexedDB object stores (IDBObjectStore) and indexes (IDBIndex) can be modified during version change transactions. Attempting to assign the name attribute at any other time causes exceptions. Motivation

Web developers can reasonably expect to be able to rename IndexedDB object stores in order to improve their code's readability. Without native rename support, developers can only implement renaming by creating a new store, copying all the relevant data from the old store, and removing the old store. This approach results in large version change transactions, leading to awful page load times.

This has been a longstanding feature request from Web developers, such as the Lovefield (https://google.github.io/lovefield/) team.

Interoperability risk Firefox: Shipped Edge: No public signals Safari: No public signals Web developers: No signals

Firefox has already implemented this API. We plan to develop Web Platform tests and verify them against their implementation.

Compatibility risk The attributes that we're adding setters to were previously read-only, so there's no compatibility risk. Ongoing technical constraints None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes OWP launch tracking bug

No OWP bug. The implementation is tracked by https://crbug.com/457447

Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5812621622116352 Requesting approval to ship? No