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

> Chrome is following the letter of the spec, that in "steps for deleting a database" the "delete pending flag" is set immediately (no waiting)

In v1 of the spec the language for deleteDatabase is "The method then queues up an operation to run the steps for deleting a database"
In v2 of the spec the language for deleteDatabase is "Queue a task to run these substeps:...Let result be the result of running the steps for deleting a database"

In both cases the "steps for deleting a database" are queued and run asynchronously. In neither case is the "delete pending flag" set immediately.

So the example code actually does the following:

indexedDB.open - "The method then queues up an operation to run the steps for opening a database."
indexedDB.open - "The method then queues up an operation to run the steps for opening a database."
indexedDB.deleteDatabase - "The method then queues up an operation to run the steps for deleting a database."

There's no mention of setting the "delete pending flag" anytime before the steps for deleting a database are executed.

Trunk WebKit and Firefox treat these as a queue as mentioned above, and I think they're right.

---
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#issuecomment-228512051