WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
66213
Web Inspector: console evaluation is possible only in the main world context
https://bugs.webkit.org/show_bug.cgi?id=66213
Summary
Web Inspector: console evaluation is possible only in the main world context
Yury Semikhatsky
Reported
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
Attachments
Add attachment
proposed patch, testcase, etc.
Jericho West
Comment 1
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
Yury Semikhatsky
Comment 2
2013-02-28 00:57:46 PST
We added context selector to the console some time ago. Closing the bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug