Closed Bug 765412 Opened 12 years ago Closed 12 years ago

IDBCursorWithValue.continue returns undefined but the spec says it should return null

Categories

(Firefox :: Untriaged, defect)

12 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 759970

People

(Reporter: danial.gibson, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725

Steps to reproduce:

When you call IDBCursorWithValue.continue and there are no more records to return, in the onsuccess handler, evt.target.result is undefined when it should be null.


Actual results:

evt.target.result was undefined


Expected results:

http://www.w3.org/TR/IndexedDB/#cursor-iteration-operation
5.7 Cursor Iteration Operation, step 3:
If found record is not defined, set cursor's key and primary key to undefined. If cursor implements IDBCursorWithValue orIDBCursorWithValueSync, then set cursor's value to undefined. The result of this algorithm is null. Abort these steps.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.