- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Apr 2013 04:24:45 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681 --- Comment #9 from Jonas Sicking <jonas@sicking.cc> --- I don't particularly care which order we define for the various functions, as long as it is defined. I guess there's some value in having a consistent ordering. For example it seems surprising that the orders between .add and .delete are so different: IDBObjectStore.add(): InvalidStateError > TransactionInactiveError > ReadOnlyError > DataError > DataCloneError IDBObjectStore.delete(): DataError > InvalidStateError > TransactionInactiveError > ReadOnlyError If the transaction-related errors are thrown after the data-related errors then it might make it easier to first process the incoming data and then call more generic functions that schedule a request against a transaction. That's not something that made sense in the current gecko implementation, but I could see that being the case elsewhere. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 1 April 2013 04:24:50 UTC