commit 18f81dcf84ee6f58e68bc12c7a5da39a1a16a140
author Ehsan Karamad <ekaramad@chromium.org> Tue Oct 16 15:12:53 2018
committer Commit Bot <commit-bot@chromium.org> Tue Oct 16 15:12:53 2018
tree 24b3437271983a68310264ef8d03dfaadee0b87a
parent 4cdc95ad6713e3ba3eec5d245a0e41c34ddee003

Support for Proxies in Frame-based MimeHandlerView

The API for attaching inner and outer WebContentses only supports a
RenderFrameHost which is same-process and origin with its parent. This
is due to the fact that all GuestViews start off with a blank <iframe>
which is later swapped out with a proxy during attaching process.

For MimeHandlerViewGuest it is not guaranteed that the starting frame
in an <embed> or <object> is in 'about:blank'. This CL circumvents the
problem by first navigating a plugin frame (on the browser side) to
'about:blank' and then proceeding with the attaching process.

 Bug: 659750

Change-Id: I57d41a38e957b22c4ba3c29cb11122115373946f
Reviewed-on: https://chromium-review.googlesource.com/c/1240635
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599986}