Bug 42554 - Web Inspector: elements from iframes should be accessible in the console
Summary: Web Inspector: elements from iframes should be accessible in the console
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2010-07-18 23:18 PDT by Yury Semikhatsky
Modified: 2014-12-16 00:27 PST (History)
14 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Yury Semikhatsky 2010-07-18 23:18:37 PDT
Currently evaluation in the console is performed in the context of the main frame in the page and it adheres to the same cross-origin policy as the main frame itself. This means that you cannot access elements in the iframe unless the main frame can. We could provide a mechanism for choosing in which iframe to perform evaluation.
Comment 1 Yury Semikhatsky 2010-07-18 23:19:35 PDT
There is a user request for this:
Comment 2 Timothy Hatcher 2010-07-19 01:06:23 PDT
Firebug does this with the grossly named cd() function.
Comment 3 George Montana Harkin 2011-02-28 08:28:58 PST
+1 for this feature. Pretty useful if developing on a legacy portal that uses iframes for everything.
Comment 4 Gabriel Hernandez 2011-03-08 14:46:29 PST
+1 This is badly needed for the new Facebook iframes app canvas. Development in this environment has been notoriously difficult thus far due to the abomination known as FBJS and this new method of making pages actually suffers only on this level, no console for my iframe forces me to use Firefox/Firebug.
Comment 5 Glen 2011-04-27 14:26:20 PDT
This is badly needed. I have a simple popup window using an iframe (using Highslide), and cannot debug inside of it. Having to resort to IE9 and Firefox :(
Comment 6 ramki 2011-07-14 02:14:26 PDT
Comment 7 Charles Pritchard 2011-07-14 03:08:34 PDT
This appears to be available in Firebug: