Chrome Version       : 57.0.2987.110
OS Version: OS X 10.11.6
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Open a chrome extension that injects an iframe with a chrome-extension:// URL into the top frame document
2. Right click on anything other than the injected frame on the current page
3. In the console drawer, click on the views dropdown and notice that you cannot see the iFrame context in the dropdown
4. Also, (see attached screenshot) the iframe element is empty in the elements view

What is the expected result?

Not only can you see and select the chrome-extension iframe context within the dropdown, console logs and network requests are all shown in the same dev tools window/tray.

What happens instead of that?

You cannot see the iframe in the views dropdown, and any console logs / network requests do not show up in the console/network tab. If you right click and inspect inside of the chrome extension iframe, it opens an ADDITIONAL chrome window for the chrome-extension:// URL

Please provide any additional information below. Attach a screenshot if
possible.

Likely caused by shipping out-of-process iframe rendering for chrome-extension:// URLS

Note: This makes perfect sense for end user / production, but introduces a disastrous road block for enterprise extension development. For someone like me who runs an external window of dev tools for both the tab and background page, forcing me to now run additional instances of dev tools for every chrome-extension frame is a major problem for an efficient development workflow.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36



 

Deleted: Screen Shot 2017-03-20 at 11.25.03 AM.png 209 KB

	Screen Shot 2017-03-20 at 11.25.03 AM.png 209 KB View Download