Bug 42554

Summary: Web Inspector: elements from iframes should be accessible in the console
Product: WebKit Reporter: Yury Semikhatsky <yurys>
Component: Web Inspector (Deprecated)Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: burg, bweinstein, chuck, gabriel, glen.little, gramki, joepeck, keishi, montana.harkin, pfeldman, pmuellr, rik, yurys, zachleatherman
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   

Yury Semikhatsky
Reported 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.
Attachments
Yury Semikhatsky
Comment 1 2010-07-18 23:19:35 PDT
Timothy Hatcher
Comment 2 2010-07-19 01:06:23 PDT
Firebug does this with the grossly named cd() function.
George Montana Harkin
Comment 3 2011-02-28 08:28:58 PST
+1 for this feature. Pretty useful if developing on a legacy portal that uses iframes for everything.
Gabriel Hernandez
Comment 4 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.
Glen
Comment 5 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 :(
ramki
Comment 6 2011-07-14 02:14:26 PDT
+1
Charles Pritchard
Comment 7 2011-07-14 03:08:34 PDT
Note You need to log in before you can comment on or make changes to this bug.