Issue 655151  has been merged into this issue.

 Issue 641777  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d61cd0b7c463ee9907c8fb90b22a11c19829e486

commit d61cd0b7c463ee9907c8fb90b22a11c19829e486
Author: dgozman <dgozman@chromium.org>
Date: Wed Nov 09 23:42:04 2016

[DevTools] Force contexts initialization in OOPIF case.

This happens when you connect DevTools to the page without context.

Previously, we checked for the main frame being a local frame.
Now we force for every local frame in the subtree.

BUG= 652783 

Review-Url: https://codereview.chromium.org/2491063002
Cr-Commit-Position: refs/heads/master@{#431082}

[modify] https://crrev.com/d61cd0b7c463ee9907c8fb90b22a11c19829e486/third_party/WebKit/Source/core/page/Page.cpp

This work is in progress and available behind an experimental feature in DevTools.

For reference, here's how to experiment with it today:
1) Enable "Developer Tools experiments" on chrome://flags, and restart.
2) Open DevTools Settings, go to Experiments tab, and press Shift 7 times.
3) Check "Auto-attach to cross-process subframes."
4) Open a new DevTools instance on a page that has an OOPIF (e.g., http://csreis.github.io/tests/cross-site-iframe-simple.html when running with --site-per-process).

 Issue 697743  has been merged into this issue.

 Issue 697126  has been merged into this issue.

Hopefully, it'll be possible to use element picker to select DOM elements interactively inside OOPIF. Currently the entire iframe element is selected in the main DOM tree of the page.

This is already possible, if you follow steps from #c8.

>This is already possible, if you follow steps from #c8.

Uhm, I did follow the steps, this thread is short enough for me to notice the instruction. A second DOM tree for OOPIF is displayed in the Elements panel but element picker can't select inside OOPIF on the test site from c#8.

Re #c19: sorry, I misunderstood what you are talking about. Indeed, that does not work. I'll fix it.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d20a42b6f8b1f703717dac5c7936223ba129e1a3

commit d20a42b6f8b1f703717dac5c7936223ba129e1a3
Author: dgozman <dgozman@chromium.org>
Date: Tue Mar 07 18:29:50 2017

[DevTools] Pass events to remote frames in inspect mode.

Before, we inspected a frame owner element for remote frame on click.
Now we clear highlight and do not consume event so that remote frame
could handle it and inspect proper node inside.

BUG= 652783 

Review-Url: https://codereview.chromium.org/2736603004
Cr-Commit-Position: refs/heads/master@{#455147}

[modify] https://crrev.com/d20a42b6f8b1f703717dac5c7936223ba129e1a3/third_party/WebKit/Source/web/InspectorOverlay.cpp

 Issue 703185  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a2a5081b066eb679783fc84c7fb4b11480ffb696

commit a2a5081b066eb679783fc84c7fb4b11480ffb696
Author: dgozman <dgozman@chromium.org>
Date: Fri May 05 01:49:00 2017

[DevTools] Enable "auto attach to sub frames" by default

Also made "Inspect Element" open DevTools for main page now.

BUG= 652783 

Review-Url: https://codereview.chromium.org/2859063002
Cr-Commit-Position: refs/heads/master@{#469568}

[modify] https://crrev.com/a2a5081b066eb679783fc84c7fb4b11480ffb696/chrome/browser/devtools/devtools_window.cc
[modify] https://crrev.com/a2a5081b066eb679783fc84c7fb4b11480ffb696/third_party/WebKit/Source/devtools/front_end/main/Main.js

The main work is done here. We are tracking the reset in separate issues.