IndexedDB createIndex() fails if more than 42 indexes

Won’t fix Issue #7121942


Apr 5, 2016
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  1. Create a new database using IndexedDB api
  2. Subscribe to the onerror and the onsuccess event.
  3. Subscribe to the onupgradeneeded event and create an object store with more than 42 indexes
  4. onerror event is fired with AbortError

Expected Results:

There should be no hard limit on the number of indexes on an object store in IndexedDB.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Saty B.”

      Changed Assigned To from “Saty B.” to “IE S.”

      Changed Status to “Won’t fix”

    • Hello,

      Thank you for providing your feedback on IE11. We are not accepting feedback on Internet Explorer through this portal any longer (unless security related). We welcome any feedback you have on Microsoft Edge through this website. If this is blocking enterprise deployment, please follow the CSS escalation process to engage MS support (GES, General Escalation Service) to file a servicing request.

      Best Wishes,
      The MS Edge Team

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

    Sign in