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 10007 - Async callbacks should fire in the same order the async requests are made in IndexedDB.
Summary: Async callbacks should fire in the same order the async requests are made in ...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Nikunj Mehta
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-24 11:43 UTC by Jeremy Orlow
Modified: 2010-10-29 17:18 UTC (History)
4 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-06-24 11:43:18 UTC 
Per the "[IndexedDB] Callback order" thread [1], we should specify the order of async callbacks (either onsuccess or onerror) to fire in the order that the async requests are made.  I.e. the same order the IDBRequest objects are returned.

[1] http://www.mail-archive.com/public-webapps@w3.org/msg09208.html
Comment 1 Jonas Sicking (Not reading bugmail) 2010-10-29 17:18:30 UTC 
Fixed by http://dvcs.w3.org/hg/IndexedDB/rev/26e7d99ab935

It's a quite complicated checkin so please do check that things look good.