This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10165 - [IndexedDB] IDBRequest.abort() should be removed
Summary: [IndexedDB] IDBRequest.abort() should be removed
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Andrei Popescu
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2010-07-14 10:37 UTC by Jeremy Orlow
Modified: 2010-08-27 09:38 UTC (History)
2 users (show)

See Also:


Description Jeremy Orlow 2010-07-14 10:37:10 UTC
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.

Comment 1 Jeremy Orlow 2010-08-25 22:44:58 UTC
Per discussion on threads, IDBRequest.abort() should simply be removed.
Comment 2 Andrei Popescu 2010-08-27 09:38:51 UTC
Fixed in