Make load events in iframe elements work with OOPIF (Chromium side).

Make load events in iframe elements work with OOPIF  (Chromium side).

Today, when the parent frame defines a load event handler in the
iframe element of an out-of-process child frame, the event does not
fire in the parent process.  This CL adds the plumbing to forward the
event from the child frame's process to the parent frame's process.

Blink side: https://codereview.chromium.org/937203003

BUG=453690
Committed: https://crrev.com/f40ce5b0e297205977af598a5ebc6c5c920c4a4a
Cr-Commit-Position: refs/heads/master@{#318101}

[alexmos, 2015-02-24 20:10:22]

alexmos@chromium.org changed reviewers:
+ nasko@chromium.org

[alexmos, 2015-02-24 20:10:23]

Nasko, do you mind reviewing this CL?  This should fix one of the two roadblocks
for running security layout tests with OOPIF (the other being postMessage).

[nasko, 2015-02-24 22:47:11]

As we chatted, it will be better if the IPC is routed through the
RenderFrameProxy instead of the parent RenderFrameHost.

https://codereview.chromium.org/954793002/diff/40001/content/renderer/render_...
File content/renderer/render_frame_impl.cc (right):

https://codereview.chromium.org/954793002/diff/40001/content/renderer/render_...
content/renderer/render_frame_impl.cc:1552: void
RenderFrameImpl::OnDispatchLoad(int subframe_routing_id) {
nit: Shouldn't we call the parameter name "proxy_routing_id"?

[alexmos, 2015-02-24 23:31:18]

Thanks, I've changed this to route through the RenderFrameProxy as we discussed.
 I really like how it simplified the renderer->browser plumbing.  Please take a
look at PS4.

https://codereview.chromium.org/954793002/diff/40001/content/renderer/render_...
File content/renderer/render_frame_impl.cc (right):

https://codereview.chromium.org/954793002/diff/40001/content/renderer/render_...
content/renderer/render_frame_impl.cc:1552: void
RenderFrameImpl::OnDispatchLoad(int subframe_routing_id) {
On 2015/02/24 22:47:11, nasko wrote:
> nit: Shouldn't we call the parameter name "proxy_routing_id"?

Routing through the proxy made this argument unnecessary.

[nasko, 2015-02-24 23:50:27]

LGTM

[alexmos, 2015-02-25 17:40:37]

The CQ bit was checked by alexmos@chromium.org

[commit-bot: I haz the power, 2015-02-25 17:41:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/954793002/80001

[commit-bot: I haz the power, 2015-02-25 17:46:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-25 17:46:43]

Try jobs failed on following builders:
  android_aosp on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/android_aosp/bu...)

[alexmos, 2015-02-25 19:07:08]

The CQ bit was checked by alexmos@chromium.org

[alexmos, 2015-02-25 19:07:08]

The patchset sent to the CQ was uploaded after l-g-t-m from nasko@chromium.org
Link to the patchset: https://codereview.chromium.org/954793002/#ps100001
(title: "Rebase")

[commit-bot: I haz the power, 2015-02-25 19:08:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/954793002/100001

[commit-bot: I haz the power, 2015-02-25 20:20:25]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2015-02-25 20:21:15]

Patchset 6 (id:??) landed as
https://crrev.com/f40ce5b0e297205977af598a5ebc6c5c920c4a4a
Cr-Commit-Position: refs/heads/master@{#318101}