14408 2011-10-07 23:37:52 +0000 [IndexedDB] Cursors .key/.primaryKey/.value shouldn't throw as soon as .continue is called 2012-02-22 18:16:28 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas jonas israelh mike public-webapps public-webapps-bugzilla oldest_to_newest 57973 0 jonas 2011-10-07 23:37:52 +0000 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. 59496 1 jonas 2011-11-02 15:47:21 +0000 I'll take this bug 60697 2 jonas 2011-11-30 20:11:24 +0000 Fixed. Cursors now keep their value until a new value is loaded, or the cursor iterates off the end. 64155 3 israelh 2012-02-15 23:00:30 +0000 Do we need to remove the following text from the IDBCursor.continue and IDBCursor.advance methods to finalize the changes to this bug: -->Before this method returns, unless an exception was thrown, it sets the got value flag on the cursor to false. 64167 4 jonas 2012-02-16 14:28:32 +0000 I think it's still needed such that calling .continue() a second time still throws. 64168 5 jonas 2012-02-16 14:29:12 +0000 Note that the 'got value' flag doesn't affect the definition of the key/primaryKey/value attributes any more. 64176 6 israelh 2012-02-16 17:32:37 +0000 Does that mean that setting the 'got value' flag to false won't prevent me from reading the cursor information that was returned to the onsuccess handler after the continue method is invoked? 64415 7 jonas 2012-02-22 12:01:30 +0000 Exactly. 64439 8 israelh 2012-02-22 18:16:28 +0000 Jonas, Thanks for the feedback. This makese sense. I'll go ahead and close the bug.