- From: Brett Zamir <notifications@github.com>
- Date: Thu, 27 Apr 2017 16:57:59 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 April 2017 23:58:32 UTC
Also, if there is an error (abort errors are the specified ones) during or after the "steps to run an upgrade transaction", should `open` not reset the `result` to `undefined` as well? Or can an error co-exist with a result? Also, as far as the explanatory text you cited mentioning the `result` possibly changing... If in `IDBFactory.open`, the "steps to open a database" are run *in parallel* with the queuing of a task to set the `result` or `error`, I would think this task to set a result for open would technically occur before the task to set a result for the upgrade (within the "steps to run an upgrade transaction"). While the open steps could clarify that the steps should wait until there is a result, the task would still have already been added to the queue before the upgrade task had been added to it. -- 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/161#issuecomment-297871047
Received on Thursday, 27 April 2017 23:58:32 UTC