121208 2013-09-11 21:06:29 -0700 Web Inspector: 'arguments' should be accessible from the console 2016-12-13 15:37:09 -0800 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All NEW InRadar P2 Normal --- 1 ggaren mark.lam fpizlo ggaren inspector-bugzilla-changes paul+bugs webkit-bug-importer oldest_to_newest 928126 0 ggaren 2013-09-11 21:06:29 -0700 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. 928127 1 webkit-bug-importer 2013-09-11 21:06:39 -0700 <rdar://problem/14972198> 1060433 2 timothy 2015-01-10 10:17:37 -0800 *** Bug 118314 has been marked as a duplicate of this bug. ***