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 10430 - [IndexedDB] We need to make it more clear IDBRequests can be reused and spec readyState's behavior
Summary: [IndexedDB] We need to make it more clear IDBRequests can be reused and spec ...
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: Jonas Sicking (Not reading bugmail)
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 14:50 UTC by Jeremy Orlow
Modified: 2010-11-08 11:34 UTC (History)
3 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-08-25 14:50:47 UTC 
http://www.w3.org/TR/IndexedDB/#idl-def-IDBRequest right now clearly assumes IDBRequests are only going to be used once.  But IDBCursor.continue() reuses them.  At the very least, we'll need to clean up the .readyState section to make it clear it's possible to go from DONE to LOADING (or we can remove it altogether?).  I think some notes explicitly pointing out that some parts of the API reuse them would be helpful as well.
Comment 1 Jeremy Orlow 2010-08-25 15:03:22 UTC 
Also, readyState's constants should probably start at 0 rather than 1.
Comment 2 Jonas Sicking (Not reading bugmail) 2010-11-01 04:52:57 UTC 
Working at rewriting cursor handling, especially related to indexes.
Comment 3 Jonas Sicking (Not reading bugmail) 2010-11-08 11:34:58 UTC 
Should be fixed by http://dvcs.w3.org/hg/IndexedDB/rev/8716288a4fe1

Would be great if someone could check that it looks correct.