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 10402 - [IndexedDB] IDBCursor.remove/update behavior when at end of range unspecified
Summary: [IndexedDB] IDBCursor.remove/update behavior when at end of range unspecified
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-19 16:23 UTC by Jeremy Orlow
Modified: 2010-11-08 11:53 UTC (History)
4 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-08-19 16:23:11 UTC 
The behavior of IDBCursor.remove and IDBCursor.update is unspecified for when the cursor is at the end of the range.  It seems clear we should raise an error, but I'm not sure which type is best.
Comment 1 Jeremy Orlow 2010-08-19 16:30:05 UTC 
Neither specifies what should returned in the result.  I'm assuming null?
Comment 2 Jonas Sicking (Not reading bugmail) 2010-11-08 11:44:09 UTC 
Comment #0 is now covered (by http://dvcs.w3.org/hg/IndexedDB/rev/8716288a4fe1)

Do we want to return null or undefined for comment #1? I've been leaning more towards undefined since these APIs don't return objects but rather values.
Comment 3 Jonas Sicking (Not reading bugmail) 2010-11-08 11:53:46 UTC 
I went with undefined.