Headless: Support Multiple tabsockets (reland)
TabSockets are intended to either be installed into the main world or
a isolated world created by Page.createIsolatedWorld. Previously we
only supported a single TabSocket per WebContents but that's unfortunate
with OOPIF. This patch lets us support multiple TabSockets up to one
per world per frame.
The mojoms have changed a bit with
TabSocket::AwaitNextMessageFromEmbedder moving to
HeadlessRenderFrameController::SendMessageToTabSocket which simplifies
recieveing a message from the embedder since a hanging IPC is no
longer needed.
Original patch: https://chromium-review.googlesource.com/c/543160/
Bug: 546953
Change-Id: Iab134b78d3cbfcbdb00ada15a6ae6d3b253727a8
TBR: jochen@chromium.org, mkwst@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/565404
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485922}24 files changed
