11

I'm using Chrome's (v21) dev tools to debug a large javascript application. While stepping through the code, I'd like to change the value of a local (function scope) variable. How do I do this?

I've tried:

  1. Clicking on the variable in the "Scope" window and editing it, hitting Enter afterward. The value changes in the Scope window as expected, but when I step to the next line, the variable then reverts back to its old value.
  2. Typing "variable = 123" in the console. After I hit Enter, the console "result" is the value I entered, but the variable itself does not change in value. If I then enter "variable" and hit Enter, the console returns the original value; the Scope window also shows the original value still.

Again, this is a local, function-scoped variable, and the current line of execution is within the same scope where the variable was defined.

This other question is essentially a duplicate, but hasn't elicited any useful answers (maybe because it's poorly written).

Community
  • 1
  • 1
GreenGiant
  • 4,930
  • 1
  • 46
  • 76
  • +1 - I've not run into a situation where I've needed to do this, but it's true, I would have expected it to work like the `immediate window` in Visual Studio. Can verify that Chrome v22 is the same. Have you looked through the Chrome bug reports to see if there's something along these lines reported? I'm sure it isn't a 'bug' per se... more just 'non-intuitive behavior' – BLSully Sep 28 '12 at 15:02
  • Using a different variation of keywords, I was able to find [another question that answers this](http://stackoverflow.com/questions/4603021/is-it-possible-to-change-javascript-variable-values-while-debugging-in-google-ch). Disappointing that you cannot do this in Chrome. :( – GreenGiant Sep 28 '12 at 15:04
  • Alas, you cannot. I'm sure there's already an open issue about that... Since a very long time. – MaxArt Sep 28 '12 at 15:19
  • I'm surprised that this is not possible in Chrome dev tools. I do this in Firebug all the time. – Kevin Boucher Sep 28 '12 at 22:01
  • Filed a [bug report](http://code.google.com/p/chromium/issues/detail?id=163207) for this. – GreenGiant Nov 28 '12 at 22:07
  • 1
    Already implemented in V8: [Issue 2399](http://code.google.com/p/v8/issues/detail?id=2399) Now Chromium's Developer Tools need to be updated: [Issue 124206](http://code.google.com/p/chromium/issues/detail?id=124206) – gabrielmaldi Mar 21 '13 at 17:48

2 Answers2

2

This feature is yet to be implemented. It is absolutely reasonable thing to do, hopefully it will be implemented soon in V8–protocol–devtools.

beefeather
  • 1,040
  • 5
  • 8
1

This apparently got fixed eventually. From the issue that @gabrielmaldi linked issue 124206:

Comment 29 by natha...@aviture.us.com on Wed, May 4, 2016, 3:19 PM EDT 51.0.2696.0 is the first [development] version that includes a build of v8 that incorporates a fix for this regression (v8 version 5.1.224 includes this fix, and 51.0.2696.0 targets v8 version 5.1.227.1).

Sinc
  • 553
  • 1
  • 8
  • 31