Fix a DomStorageEvent bug with reporting the wrong connection_id to renderers.

Fix a DomStorageEvent bug with reporting the wrong connection_id to renderers and avoid sending session storage events across process boundaries.

BUG=128482
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=137985

[michaeln, 2012-05-18 01:42:34]

hi david, can you take a look at this one?

http://codereview.chromium.org/10391196/diff/4004/content/browser/dom_storage...
File content/browser/dom_storage/dom_storage_message_filter.cc (left):

http://codereview.chromium.org/10391196/diff/4004/content/browser/dom_storage...
content/browser/dom_storage/dom_storage_message_filter.cc:82: int connection_id
= IPC::MessageIterator(message).NextInt();
This reads the wrong value when invoked on 'sync' messages.

[michaeln, 2012-05-18 20:18:11]

https://chromiumcodereview.appspot.com/10391196/diff/4004/content/browser/dom...
File content/browser/dom_storage/dom_storage_message_filter.cc (left):

https://chromiumcodereview.appspot.com/10391196/diff/4004/content/browser/dom...
content/browser/dom_storage/dom_storage_message_filter.cc:82: int connection_id
= IPC::MessageIterator(message).NextInt();
On 2012/05/18 01:42:34, michaeln wrote:
> This reads the wrong value when invoked on 'sync' messages.

sync messages are serialized differently than async messages, they have an
additional header... NextInt() is reading a value from that header instead of
the first param of the serialized method params

[michaeln, 2012-05-18 21:54:29]

hi josh, since david's out can you take a look?

[jsbell, 2012-05-18 22:08:58]

lgtm