$0 doesn't work for iframes
Reported by
kdzwinel@gmail.com,
Aug 1 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Steps to reproduce the problem: 1. go to http://jsbin.com/?html,js,output 2. In the elements tab select any iframe 3. Type "$0" in the console What is the expected behavior? node details should be displayed in the console What went wrong? "null" is displayed instead Did this work before? N/A Chrome version: 52.0.2743.82 Channel: stable OS Version: OS X 10.11.5 Flash Version:
,
Aug 2 2016
Looks like we don't set the frameOwner element to be an inspected object.
,
Aug 3 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c43dd9a10d97cad56ac0d8780ac93947a0edeb4f commit c43dd9a10d97cad56ac0d8780ac93947a0edeb4f Author: lushnikov <lushnikov@chromium.org> Date: Wed Aug 03 20:23:55 2016 DevTools: make iframe nodes report correct frame they belong to Technically, the iframe node belongs to the parent frame. The patch changes the WI.DOMNode.frameId method to correspond to this logic. BUG= 633167 R=dgozman Review-Url: https://codereview.chromium.org/2206153002 Cr-Commit-Position: refs/heads/master@{#409611} [modify] https://crrev.com/c43dd9a10d97cad56ac0d8780ac93947a0edeb4f/third_party/WebKit/LayoutTests/inspector/elements/selected-element-changes-execution-context-expected.txt [modify] https://crrev.com/c43dd9a10d97cad56ac0d8780ac93947a0edeb4f/third_party/WebKit/LayoutTests/inspector/elements/selected-element-changes-execution-context.html [modify] https://crrev.com/c43dd9a10d97cad56ac0d8780ac93947a0edeb4f/third_party/WebKit/Source/devtools/front_end/sdk/DOMModel.js
,
Aug 4 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by eostroukhov@chromium.org
, Aug 2 2016Status: Assigned (was: Unconfirmed)