12114 2011-02-18 00:02:28 +0000 Blocked setVersion transactions should be aborted when their database is closed 2011-03-08 00:50:11 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jorlow dave.null mike public-webapps public-webapps-bugzilla oldest_to_newest 45791 0 jorlow 2011-02-18 00:02:28 +0000 On Thu, Feb 17, 2011 at 3:58 PM, Pablo Castro <Pablo.Castro@microsoft.com> wrote: >> What if you have two database connections open and both do a setVersion transaction and one calls .close (to yield to the other)? Neither can start until one or the other actually is closed. If a database is closed (not just close pending) then I think we need to abort any blocked setVersion calls. If one is already running, it should certainly be allowed to finish before we close the database. This sounds reasonable to me (special case and abort the transaction only for blocked setVersion transactions). We should capture it explicitly on the spec, it's the kind of little detail that's easy to forget.