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 11187 - [IndexedDB] Repeated calls to IDBCursor.continue() should throw
Summary: [IndexedDB] Repeated calls to IDBCursor.continue() should throw
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-11-01 11:52 UTC by Jeremy Orlow
Modified: 2010-11-08 11:34 UTC (History)
3 users (show)

See Also:


Attachments

Description Jeremy Orlow 2010-11-01 11:52:09 UTC
If IDBCursor.continue() is called after a previous .continue() call but before its onsuccess/onerror call, we should throw a NOT_ALLOWED_ERR.  This was discuseed on list in replies to bug 10430's filing.
Comment 1 Jonas Sicking (Not reading bugmail) 2010-11-01 12:01:06 UTC
I'll work this into my current cursor rewrite.
Comment 2 Jonas Sicking (Not reading bugmail) 2010-11-08 11:34:57 UTC
Should be fixed by http://dvcs.w3.org/hg/IndexedDB/rev/8716288a4fe1

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