1284219 - Storage inspector should support non-string keys in IndexedDB records

Status: NEW

(DevTools :: Storage Inspector, defect, P3)

Description

[Jarda Snajdr [:jsnajdr]]

Steps to reproduce:
Create an IndexedDB object store where records have the following IDs:
- 1 (number)
- "1" (string)
- [1] (array)

Actual result:
- the keys in the three rows are indistinguishable (their string representation is identical)
- selecting and removing rows is broken, because the mapping between the keys and their string representation is not 1:1

All possible data types for IndexedDB record keys are described here:
https://w3c.github.io/IndexedDB/#key-construct

Comment 1

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

IndexedDB also supports compound keys, which we should support at some point.

Comment 2

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Valid key types are:

  - Numbers, except NaN. This includes Infinity and -Infinity.
  - Date objects, except where the [[DateValue]] internal slot is NaN.
  - Strings.
  - ArrayBuffer objects (or views on buffers such as Uint8Array).
  - Arrays objects.