[go: nahoru, domu]

WebContents and WebContentsObserver should not provide IPC::Sender API.

With the introduction of OOPIFs, WebContents can span multiple processes
- there is no default process to send IPC messages to.  Removing the
WebContents::Send and WebContentsObserver::Send methods forces the
callers to explicitly specify the target of the message.  This helps
avoid situations where an IPC message is sent via RenderViewHost (i.e.
to the process hosting the main frame) when it should have been send to
a process hosting a specific frame (this CL fixes a few such cases).

Bug: 663029
Change-Id: I16980f5ef05a8ac7da365edf7a92ce46677a8c0c
Reviewed-on: https://chromium-review.googlesource.com/630416
Reviewed-by: Gene Gutnik <gene@chromium.org>
Reviewed-by: Selim Gurun <sgurun@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Commit-Queue: Ɓukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500170}
23 files changed