10165 2010-07-14 10:37:10 +0000 [IndexedDB] IDBRequest.abort() should be removed 2010-08-27 09:38:51 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jorlow andreip mike public-webapps public-webapps-bugzilla oldest_to_newest 36835 0 jorlow 2010-07-14 10:37:10 +0000 As discussed in the thread "[IndexedDB] IDBRequest.abort on writing requests" [1], it's dangerous to allow IDBRequest.abort() to be called on any request that has side effects. The best solution brought up in the thread was to have it throw if you call it on any request that isn't read only. But later on in the thread, I think it became fairly questionable that IDBRequest.abort() provides any value in the current spec since none of the read only operations should be particularly long running and in the few cases where you might truly need to do an abort, you can simply roll back the transaction. [1] http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0190.html 37864 1 jorlow 2010-08-25 22:44:58 +0000 Per discussion on threads, IDBRequest.abort() should simply be removed. 37989 2 andreip 2010-08-27 09:38:51 +0000 Fixed in http://dvcs.w3.org/hg/IndexedDB/rev/b7ae74e39c82