IndexedDB requires sequential access to and IDBFactory.deleteDatabase - by Nolan Lawson

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 866489 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/3/2014 12:46:18 PM
Access Restriction Public


There appears to be a race condition within IE's implementation of IndexedDB that prevents simultaneous access to and IDBFactory.deleteDatabase, even for databases with different names. The "open" request's onsuccess, onblocked, and onerror callbacks are never fired.

The workaround is to queue all access to and IDBFactory.deleteDatabase, but this is painful from a developer's point of view and is not required on Chrome or Firefox.
Sign in to post a comment.
Posted by Microsoft on 4/4/2016 at 11:35 AM
We've moved! This issue is now being tracked at
Posted by Microsoft on 5/5/2014 at 10:42 AM
Thank you for your feedback!

We will be investigating this issue further.

Best Regards,
The Internet Explorer Team