Bug 121208
| Summary: | Web Inspector: 'arguments' should be accessible from the console | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Geoffrey Garen <ggaren> |
| Component: | Web Inspector | Assignee: | Mark Lam <mark.lam> |
| Status: | NEW | ||
| Severity: | Normal | CC: | fpizlo, ggaren, inspector-bugzilla-changes, paul+bugs, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Geoffrey Garen
It's currently inaccessible because of the scope the Web Inspector sets up before evaluating code. See <http://trac.webkit.org/browser/trunk/Source/WebCore/inspector/InjectedScriptSource.js#L559>.
The steps to fix this are:
(1) Refactor console scope to allow 'arguments' access again.
(2) Change the activation object to always provide an 'arguments' property, but perform eager tear-off if the user program didn't use the arguments object.
To avoid regressing bug 121206, and allocating the arguments object when it wasn't used:
(3) Provide a per-callFrame flag that specifies whether the user program used the arguments object.
(4) ScopeChainDetailsSidebarPanel should make an "excludedProperties" array (the inverse of extraProperties). If the flag is false, it should add 'arguments' to the excludedProperties array.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/14972198>
Timothy Hatcher
*** Bug 118314 has been marked as a duplicate of this bug. ***