Open Bug 1284219 Opened 8 years ago Updated 2 years ago

Storage inspector should support non-string keys in IndexedDB records

Categories

(DevTools :: Storage Inspector, defect, P3)

defect

Tracking

(firefox50 affected)

Tracking Status
firefox50 --- affected

People

(Reporter: jsnajdr, Unassigned)

References

(Blocks 1 open bug)

Details

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
IndexedDB also supports compound keys, which we should support at some point.
Priority: -- → P3
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.
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.