[w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79)

Consider: 

```js
indexedDB.open(name).onsuccess = e => {console.log('open1'); e.target.result.close(); };
indexedDB.open(name).onsuccess = e=>{ console.log('open2'); e.target.result.close(); };
indexedDB.deleteDatabase(n).onsuccess = e => { console.log('delete'); }
```

* Firefox logs: open1, open2, delete.
* Chrome logs: open1, delete, open2

IIRC we discussed this before. Chrome is following the letter of the spec, that in "steps for deleting a database" the "delete pending flag" is set immediately (no waiting) and in "steps for opening a database" the steps wait on the "delete pending flag". Firefox instead processes IDBOpenDBRequests (opens, deletes) on a named database as a FIFO queue.

This is an observable incompatibility, so we should probably standardize the behavior one way or the other.


---
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/79