IndexedDB: Send cursor data along with success messages

IndexedDB: Send cursor data along with success messages

Chromium already behaves like this in the IPC plumbing for IDB,
but the code can be simplified by pushing this into the WebKit
implementation itself.

Full landing sequence is:

(1) WebKit prep: Add new API stubs http://webkit.org/b/92414 
(2) Chromium changes: dispatch to old and new API https://chromiumcodereview.appspot.com/10830028 (this patch)
(3) WebKit changes: use the new API http://webkit.org/b/92278
(4) Chromium cleanup: delete old API usage
(5) WebKit changes: delete old API


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=150883

[jsbell, 2012-07-30 23:28:17]

dgrogan@ - ptal

[dgrogan, 2012-07-31 17:19:18]

LGTM

Does this sequence of changes cause any behavior change?  If not, do you want to
wait until after the freeze next monday to land this, on the off-chance that it
regresses something?  

Maybe I'm showing ignorance, but ever since prefetching went in I'm always
nervous about cursor changes having unforeseen side effects.

[jsbell, 2012-08-01 01:00:00]

On 2012/07/31 17:19:18, dgrogan wrote:
> Does this sequence of changes cause any behavior change?

Nope!

>  If not, do you want to
> wait until after the freeze next monday to land this, on the off-chance that
it
> regresses something?  

Yep, it can wait. 

> Maybe I'm showing ignorance, but ever since prefetching went in I'm always
> nervous about cursor changes having unforeseen side effects.

No kidding. :) I think I've only broken perefetching once...

I understand perefetching better after doing this patch, though.

[commit-bot: I haz the power, 2012-08-09 18:36:50]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jsbell@chromium.org/10830028/2002

[commit-bot: I haz the power, 2012-08-09 20:30:50]

Change committed as 150883