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

@malibuzios Those are bugs in Edge and we should fix them. (I filed those issues, and now I work for Microsoft. :smiley:)

I agree with @inexorabletash that we shouldn't change the spec to work around implementation bugs. And FWIW, some stability issues have indeed been fixed between Edge 13 and 14, but no work is planned for IE.

> Maybe someone has already reduced the specific error case and shared a workaround on e.g. StackOverflow ?

Essentially you have to serialize all open/close operations on IDB in IE/Edge, per db name. (I.e. you must wait for any `open()`/`deleteDatabase` operations to complete before starting a new one). In Pouch we worked around this by [keeping a global store keyed by database name](https://github.com/pouchdb/pouchdb/blob/a3d76ad6ee87655d8721ea8926d8f0a1533875e6/packages/node_modules/pouchdb-adapter-idb/src/index.js#L796-L828).

There's a test case linked in each of those MS issues, although IIRC they're not very reduced.

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