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 14405 - Steps for firing success/error events on a request are very transaction-centric
Summary: Steps for firing success/error events on a request are very transaction-centric
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-07 17:27 UTC by Kyle Huey
Modified: 2011-11-01 21:44 UTC (History)
3 users (show)

See Also:

Attachments

Description Kyle Huey 2011-10-07 17:27:02 UTC 
e.g. http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#dfn-fire-a-success-event

In particular, this obscures the fact that if a success event handler throws on a request that has no transaction (e.g. IDBOpenDBRequest) there is no error event fired (because that error event is fired from the steps for aborting a transaction, and there is no transaction to abort).
Comment 1 Kyle Huey 2011-10-07 17:28:55 UTC 
Also, should we be firing the error event at the request anyways in this case?
Comment 2 Jonas Sicking (Not reading bugmail) 2011-11-01 21:44:51 UTC 
I've fixed this already