17643 2012-06-28 22:22:25 +0000 What should transaction.error be set to if a error handler throws an exception 2012-07-15 09:20:58 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas dave.null mike odinho public-webapps public-webapps-bugzilla oldest_to_newest 69516 0 jonas 2012-06-28 22:22:25 +0000 The most basic question is, what should happen in the following scenario: objectStore.add("value", 1); // succeeds req = objectStore.add("value", 1); // will fail due to key collision req.onerror = function(e) { throw; } This should obviously abort the transaction, but should transaction.error.name return "ConstraintError" or "AbortError". I don't have a strong opinion. It sort of feels like the exception does override normal behavior, so we should set it to "AbortError". 69517 1 jonas 2012-06-28 22:23:19 +0000 A slightly less ambiguous case is objectStore.add("value", 1); // succeeds req = objectStore.add("value", 1); // will fail due to key collision req.onerror = function(e) { e.preventDefault(); throw; } Here it seems more clear that setting transaction.error to a "AbortError" is the right thing to do. 69518 2 jonas 2012-06-28 22:43:07 +0000 One way to look at it is that for a normal function call, an exception overrides any return values. 69598 3 odinho 2012-07-03 16:24:15 +0000 If I was writing a test for that, I'd check for AbortError. So guess I vote for that. (The exception inside a handler has consequences stuff always felt a bit weird, tho ;-) ) 70010 4 jonas 2012-07-15 09:20:58 +0000 http://dvcs.w3.org/hg/IndexedDB/rev/aab14b0951ca