Introduce API for external handling of plugins
When the contents of a plugin element (<embed> and <object>) are to be handeld externally inside an extension (most notably PDF) we currently use browser plugin. BrowserPlugin is used to render GuestView contents in another process. However, BrowserPlugin-based guest views have been deprecated and all guest views except for MimeHandlerViewGuest are not implemented on top of cross-process frames. This CL introduces the first steps in fully replacing BrowserPlugin with corss-process frames. Different mechanisms for this project have already been discussed in the design doc: https://docs.google.com/document/d/10g7Y9cprYKkch9JZ0TBUWaEnHBJT1nzhskQIt1nHbWM/edit#heading=h.ue5a8s290yhk Bug: 659750, 330264 Change-Id: If273fbbab3e9f4a4591c61b19d54e4cca73c3464 Reviewed-on: https://chromium-review.googlesource.com/1101161Reviewed-by:Ehsan Karamad <ekaramad@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#578554}
Showing
Please register or sign in to comment