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

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

--- Comment #8 from Joshua Bell <jsbell@google.com> ---
I spun up a public-script-coord thread at
http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0490.html

Consensus for this feature seems to be that it should be a new method (e.g.
continueWithPrimaryKey) rather than an overload.

...

Any thoughts on polyfilling this? It seems like you'd need to override the
built-in openCursor methods to capture the IDBRequest, and when
continueWithPrimaryKey is called the polyfill would "unhook" the success
handler (so this assumes you're using request.onsuccess not
request.addEventListener), iterate the cursor, then reattach the success
listener and call it with the event.

Re-using the request for cursors appears to be a design flaw here. :(

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

Received on Wednesday, 28 August 2013 16:35:47 UTC