Re: [IndexedDB] Consider adding some signaling method to notify on the completion of an IDBDatabase.close() operation (#72)

I'm having some doubts about these "operation blocked" errors on IE11 so I felt I might as well ask it here:

The spec does not mention there should be any problem closing a database connection (or perhaps even leaving it open?) and then immediately opening **a different one** with a higher version number and then mutating the database structure on the "onupgradeneeded" event (say, adding a new object store or an index), so I can't really tell if the problem I've encountered is specific to IE11 or is by design and according to the spec (it doesn't seem to occur on either Chrome/Firefox or latest Edge). 

In any case, being able to capture the database connection "true" close time would seem like a useful piece of information, even if it may not completely essential in practice.

---
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-198888834