IndexedDB does not support complex keys

External Issue #175639


May 6, 2014
This issue is public.
Found in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce



Repro Steps:

Here’s a live example you can use to debug: . The associated Gist also has a README that explains what you should expect to see:

Notice that the script gives the correct output in Firefox 29 and Chrome 34, but not IE11. I tested specifically in IE 11.0.9600.16538 on Windows 8.1.

Expected Results:

Complex keys are supported (see links below for details).

Actual Results:


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “IPBS P.”

      Changed Assigned To from “IPBS P.” to “Bruce M.”

      Changed Assigned To to “Kamen M.”

      Changed Assigned To from “Kamen M.” to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Shawn P.”

      Changed Assigned To from “Shawn P.” to “Ben H.”

      Changed Status to “External”

      Changed Steps to Reproduce

    • Another test performed in Microsof Edge 38.14393.0.0

      Test result:

      Demonstrating basic IndexedDB specification conformance (and failures in IE 10+11)

      Running on: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393

      This browser does not support using array keyPaths: DataError
      This browser does not support using array keys: DataError
      This browser supports puts when compound indexes are present.
      This browser does not support lookup of objects via compound index: DataError
      This browser supports storing objects using dotted keyPaths.
      This browser supports retrieving objects stored using dotted keyPaths.

    You need to sign in to your Microsoft account to add a comment.

    Sign in