IndexedDB does not accept keys longer than 888 characters

Confirmed Issue #5333188 • Assigned to Shawn P.


Nov 5, 2015
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Set a key with over 889 or more characters and value “a” and then a key with the first 888 characters of the first key with value "b". Retrieve the two keys’ values and compare the two values. They should be different but are the same:

Expected Results:

Keys can be of an (effectively) infinite length.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To from “Kamen M.” to “Shawn P.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Shawn P.” to “James M.”

      Changed Assigned To from “James M.” to “Shawn P.”

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

    Sign in