@v8js @bmeurer @mathias - Is their some reason why Chrome Dev tools can't access the outer scope. Seems like it should still be in scope.pic.twitter.com/qKkPzjeoyw
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
The v8 engine knows what the value is; but the debugger doesn't. In this example; eval got the value and returned it -- but while in inner() the debugger still has no clue.pic.twitter.com/CXsF46Uuen
So would this be something you think a feature request to enhance the tooling to change it to work the way a developer would assume it would work. (i.e. child scopes can see parent scope values, just like code can. )
I should probably be extra clear; if you mouse over the oValue; it is still undefined in the above picture; even though `eval` returned the value...
I see. The hover-over mechanism is a little broken... Notice that if you declare "var iValue = 'y'" outside of inner (in onLoad) and hover over during "debugger" you'll actually get 'test' instead of 'y' since the context of the debugger statement is applied to all variables...
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.