[Bug 14408] New: [IndexedDB] Cursors .key/.primaryKey/.value shouldn't throw as soon as .continue is called

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14408

           Summary: [IndexedDB] Cursors .key/.primaryKey/.value shouldn't
                    throw as soon as .continue is called
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jonas@sicking.cc
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Currently the 'got value' flag is set to false as soon as .continue() is
called. This makes it awkward to call .continue() at the top of your success
handler and then have several different branches that do different things
depending on the data since each branch has to take care to call .continue() at
the end.

Instead we should let cursors keep their current value until the success/error
event is fired, at which point their values are updated.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Friday, 7 October 2011 23:37:54 UTC