[Webkit-unassigned] [Bug 59474] Web Inspector: [protocol] evaluate* methods should accept 'additional context' param

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=59474





--- Comment #2 from Peter Rybin <peter.rybin at gmail.com>  2011-04-26 15:42:48 PST ---
(In reply to comment #1)
> In your example, where is the user getting the objectId value of 5 from?  From exploring some other object?  I find it hard to imagine that people would use this sort of functionality.
> 
> Here's what I'd run, in the console.
> 
>    x = nextRandomColor()
>    String(x)
> 
> After typing the first line, you can explore the result a bit.  Then type the second line and explore that a bit.
> 
> It has the side effect of setting an "x" variable in some scope (presumably global scope).  But I rarely care about that.
> 
> Do you have another use case?

It is needed for Eclipse-based client, which doesn't have console. The Eclipse UI assumes that you can point to any value (in Variables or Expressions views) and you see its string representation. Other feature is to "pin-point" any value as a global object property
( http://code.google.com/p/chromedevtools/wiki/EclipseDebuggerFeatures ).

The "non-user expression" (one with id) is generated. That's how Java client manipulates values (except for looking up properties, which is done by a dedicated protocol command).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.