WebView and WebWidget changes for out-of-process <iframe>s

[Daniel Cheng]

Hi all,

I notice there's been some confusion around how the Blink architecture (in particular, layout and painting) interacts with out-of-process iframes (OOPI).

I've written an overview of how input/layout/painting responsibilities for out-of-process child frames are now handled by WebFrameWidget rather than the WebView: https://docs.google.com/document/d/1CfoWjeq9KNNnb5HEG4_FvEu_9WWhIRzYwZDbXZRtdSQ/edit#

I've also written a separate doc covering the current work to de-WebWidget WebView: https://docs.google.com/document/d/119DUgqgVLAjVizYFaaAtQqH44Dt2Q8MIiC32pvUI3Eg/edit This work aims to remove WebWidget inheritance from WebView. Instead, the main frame's WebFrameWidget will handle its duties. This is important so Blink can use a uniform model for input/layout/painting across main frames and sub frames.

Questions, comments, feedback welcome.

Daniel

[Dimitri Glazkov]

Thank you for sharing this, Daniel!

Is there any chance we could update or delete the respective pages on dev.chromium.org?

http://dev.chromium.org/developers/design-documents/oop-iframes/oop-iframes-rendering is really, really old.

:DG<