Bug 66213 - Web Inspector: console evaluation is possible only in the main world context
Summary: Web Inspector: console evaluation is possible only in the main world context
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-14 23:56 PDT by Yury Semikhatsky
Modified: 2013-02-28 00:57 PST (History)
11 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yury Semikhatsky 2011-08-14 23:56:58 PDT 
At the moment console evaluation is possible only in the main world context. The only way to perform evaluations in a script from an isolated world(e.g. content scritps in Chromium) is to set a breakpoint/insert debugger statement. These contexts should be provided in the context selector at the bottom of the console.

Original user question: http://stackoverflow.com/questions/7055830/how-to-get-to-sandboxed-environment-of-content-script-in-chrome-js-console
Comment 1 Jericho West 2011-08-29 20:00:28 PDT 
cc: mihaip@chromium.org, e308ad5e...@yahoo.com, et al
OS: All platforms
Browser: Chrome v15 Canary (Trunk)
Status >> Request
Severity >> P4 Enhancement
Issue: Allow more debugging capabilities for content scripts).

REFERENCE
"Issue 91339 - chromium - unable to debug my content script - An open-source browser project to help move the web forward. - Google Project Hosting" - http://code.google.com/p/chromium/issues/detail?id=91339
Comment 2 Yury Semikhatsky 2013-02-28 00:57:46 PST 
We added context selector to the console some time ago. Closing the bug.