Re: [w3c/IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72)

@inexorabletash 

Thank you for your patience and assistance. I have implemented the suggestions you've recommended for dealing with the `block` event. This has improved the reliability of my library, which now also works in web workers.

The particular problem with IE11 (and IE10 as well apparently) has also been noticed by the developers of PouchDB:

See section 2: [IE has race conditions in IndexedDB](https://pouchdb.com/2014/10/26/10-things-i-learned-from-reading-and-writing-the-pouchdb-source.html)

There are several bugs they reported to Microsoft. I believe the ones I was describing here were these two:

["IndexedDB gets corrupted and stops responding"](https://connect.microsoft.com/IE/feedbackdetail/view/1009247)
["IndexedDB requires sequential access to IDBFactory.open and IDBFactory.deleteDatabase"](https://connect.microsoft.com/IE/feedbackdetail/view/866489)

Another one is this:

["IndexedDB does not call back IDBFactory.open within Web Worker"](
https://connect.microsoft.com/IE/feedbackdetail/view/866495)

Although I have relatively successful tests for IE11 in web worker (though my tests are probably not as thorough as PouchDB's), actually it is Edge so far that have proven less stable there (regardless, my whole test suite consistently crashes edge even when all indexeddb and web worker tests are disabled and I have pretty high confidence it is not really related to my code. This has proven extremely difficult to track but I may report it to Microsoft at some point).

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/72#issuecomment-207959812