[Bug 20257] IDBCursor should walk on secondary ordering of index value

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257

--- Comment #2 from Joshua Bell <jsbell@google.com> ---
So let's say you had this index:

index key primary key
========= ===========
"a" ..... 1
"a" ..... 2
"a" ..... 3
"b" ..... 1
"b" ..... 2
"b" ..... 3
"b" ..... 4

Assume an API of the form:

void continue(optional any key, optional any primaryKey);

If you have a cursor pointing at the second index entry (index key = "a",
primary key = 2), what would you expect the outcome of these operations to be -
including exception, new cursor position (key/primary key) or null?

cursor.continue() => { key: "a", primaryKey: 3 }
cursor.continue("a") => exception (key is less than or equal to current key)
cursor.continue("b") => { key: "b", primaryKey: 1 }
cursor.continue("c") => null
cursor.continue("a", 3) => ???
cursor.continue("a", 4) => ???
cursor.continue("b", 1) => ???
cursor.continue("b", 4) => ???
cursor.continue("b", 5) => ???
cursor.continue("c", 1) => ???
cursor.continue(null, 1) => ???
cursor.continue(null, 2) => ???
cursor.continue(null, 3) => ???
cursor.continue(null, 4) => ???
cursor.continue(null, 5) => ???

Are there other "interesting" cases that I'm missing?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 26 August 2013 22:22:17 UTC