Bug 148514 – Web Inspector: Suppress cross-origin restrictions when accessing $0 from the console

• Status: RESOLVED
• Resolution: INVALID
• Component: Web Inspector

[Nikita Vasilyev]

Created attachment 260037 [details]
[Image] Current behavior

Steps:
1. Open http://codepen.io/NV/pen/AKnov?editors=001
2. Inspect the SVG pie
3. Type dir($0)
4. Expand the result

Actual (on the attached image too):
> dir($0)
[Error] Blocked a frame with origin "http://codepen.io" from accessing a frame with origin "http://s.codepen.io". Protocols, domains, and ports must match.
< ▼ path#angle_arc {}
No properties.

Expected:
> dir($0)
< ▼ path#angle_arc {pathLength: SVGAnimatedNumber, ...}
(a bunch of properties)

[Radar WebKit Bug Importer]

<rdar://problem/22451638>

[Joseph Pecoraro]

This seems like expected behavior to me.

Switching the Console's Execution Context from "Main Frame" to "CodePen – index.html" eliminates the error and makes it work. In fact now, attempting to access the element from the Main Frame results in `null`, while accessing it on the sub-frame results in the Element.

I'm going to move this to Behaves Correctly. However if you have ideas about how we can improve this situation for developers those would be good enhancements to file. For instance, we may want to give elements in a sub-frame a Context Menu to change the console to that Execution Context. Already "Log Element" does the right thing.