[Webkit-unassigned] [Bug 122764] New: Web Inspector: Avoid using Runtime.executionContextCreated to figure out the iframe's contentDocument node.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 14 10:57:45 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=122764
Summary: Web Inspector: Avoid using
Runtime.executionContextCreated to figure out the
iframe's contentDocument node.
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: achicu at adobe.com
CC: timothy at apple.com, joepeck at webkit.org,
webkit-bug-importer at group.apple.com, graouts at apple.com
Runtime.executionContextCreated is only called if you have a <script> tag in the page, so iframes with no scripting will not show up in the WebInspector.
Also, it means that the console will not be able to inject any other script inside the iframe, so maybe we just need to always create a scripting context when the web inspector is loaded.
Note that it happens to work in Safari because of the do-not-track feature that will always create an exceution context for all pages. However, that's not the case for the test runner.
The context is created because of the following function call Safari::BrowserBundlePageController::injectDoNotTrackDOMPropertyInStandardWorld().
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list