Bug 66213
| Summary: | Web Inspector: console evaluation is possible only in the main world context | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Yury Semikhatsky <yurys> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | apavlov, bweinstein, e308ad5e31abe3e9525d439c603f8a96, joepeck, keishi, loislo, mihaip, pfeldman, pmuellr, rik, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Yury Semikhatsky
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
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
We added context selector to the console some time ago. Closing the bug.