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

I re-read your response and not sure exactly about what was meant here:
> Note that "blocked" events will fire if an upgrade is attempted but the connections aren't closed. That's not an error - it is just telling you that the connections didn't close yet. If they do all close — e.g. in response to the "versionupgrade" events they should receive — then the upgrade can proceed merrily.

Did you mean that the behavior displayed in the test code I provided is by design? i.e. the `blocked` event does not signify the failure of the `open` event, but I should ignore it and wait for the other events to proceed?

If that is the case, then how is it possible to differentiate between a "temporary" block - for which I'm supposed to wait for further events, and a "fatal" one meaning a connection is open somewhere (say in another tab or frame) and essentially nothing can be done?

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