16441 2012-03-19 20:12:35 +0000 Spec should note that onsuccess shouldn’t be used for writes. 2012-07-16 21:49:56 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC Linux RESOLVED FIXED P2 normal --- 1 yonathan dave.null eliotgra jonas mike odinho public-webapps public-webapps-bugzilla oldest_to_newest 65775 0 yonathan 2012-03-19 20:12:35 +0000 You generally should listen to the transaction’s “complete” event instead of the put/add request’s “success” event, because the transaction may fail after “success.” There’s at least one example of someone being confused by the wording[1]. Perhaps the spec should point out that you usually want to listen to “complete” for write requests. Use of a write request’s “success”/“error” events is probably reserved for advanced use cases (e.g. to commit part of a transaction even when the later requests fail, or to retry a write that failed, or to measure progress when a transaction has multiple parts). [1]: https://developer.mozilla.org/en/IndexedDB/Using_IndexedDB 70022 1 jonas 2012-07-16 00:40:02 +0000 Note that there are cases where listening for onsuccess is needed. For example if you are worried that a written entry might collide with an already existing one. In this case you might want to hold off further operations until the doubtful request has succeeded. 70029 2 eliotgra 2012-07-16 21:49:56 +0000 Added this note to Transaction.oncomplete and also for IDBObjectstore.add(). To determine if a transaction has completed successfully, listen to the transaction’s complete event rather than the IDBObjectStore.add request’s success event, because the transaction may still fail after the success event fires.