- From: Joshua Bell <notifications@github.com>
- Date: Fri, 21 Apr 2017 11:29:49 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 21 April 2017 18:30:59 UTC
I think to fix this properly will require: * A database may have an associated upgrade transaction, initially null * Set database's associated upgrade transaction in the steps for running an upgrade transaction * In the steps to commit/abort a transaction, in the queued task just before we fire the event, we clear the database's associated upgrade transaction This is because right after calling abort() we would consider the transaction "finished" but yet implementations still give TransactionInactiveError. Implementations still consider the database to have an associated upgrade transaction until the commit/abort actually fires. The current "... the upgrade transaction associated with database..." text is squishy since a transaction always has an associated database even after it is finished. So that would invert to "... the database's associated upgrade transaction..." -- 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/192#issuecomment-296268076
Received on Friday, 21 April 2017 18:30:59 UTC