141475 2015-02-11 08:21:34 -0800 Web Inspector: silent failure if introducing local variable in console when debugger paused 2016-12-13 15:33:46 -0800 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All NEW InRadar P2 Normal --- 1 burg webkit-unassigned ggaren inspector-bugzilla-changes jonowells mark.lam saam webkit-bug-importer oldest_to_newest 1068362 0 burg 2015-02-11 08:21:34 -0800 When the debugger is paused, running > var x = 42; in the console will not actually assign x to a local variable. This is fine, except that the command silently fails. If you later type > x while still paused, a TypeError will be thrown. This is confusing if you don't know how the console/debugger is implemented. So, should an error be thrown when a variable is introduced when debugger is paused, or should this work somehow? 1068363 1 webkit-bug-importer 2015-02-11 08:21:54 -0800 <rdar://problem/19796707> 1068400 2 saam 2015-02-11 10:47:50 -0800 I would expect this to just work while debugging. 1068636 3 timothy 2015-02-12 09:24:54 -0800 To work with strict mode we have to make a closure and call eval() inside it while paused in the debugger. http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/inspector/InjectedScriptSource.js#L409 The closure captures the var and it is thrown away each time. We could potentially reuse it while paused. But we really just need JSC support to avoid this hack. It we could use with() while in strict mode, then we wouldn't need the closure. 1195179 4 joepeck 2016-05-20 11:42:28 -0700 So this code has changed a bunch. I believe doing `var x` will work outside of strict mode code. Using `let x` probably won't work in strict or non-strict. And `var` probably won't work in strict mode. If we wanted this to work, we'd probably have to do some really tricky stuff. How do debuggers like lldb make this work? They store the result in a temporary variable, or you can create custom variables. Maybe we could approach this problem from that angle.