DevTools: Allow setting -0 value to object property

DevTools: Allow setting -0 value to object property

BUG=321560
R=pfeldman, vsevik

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=162991

[pfeldman, 2013-11-23 15:58:13]

https://codereview.chromium.org/83383002/diff/40001/Source/devtools/protocol....
File Source/devtools/protocol.json (right):

https://codereview.chromium.org/83383002/diff/40001/Source/devtools/protocol....
Source/devtools/protocol.json:3178: { "name": "forceObjectId", "type":
"boolean", "optional": true, "hidden": true, "description": "If true, will
generate a <code>RemoteObject.objectId</code> even for primitive values. The
call site is responsibile for releasing this object." },
I don't think it is a good idea since it makes protocol more complex. We either

1) need to pass these values as handles at all times (i.e. have this set to
true), or
2) serialize special values in strings when encoding them in JSON.

Both are a lot of work due to the following assumptions:
1) when remoteObject.type is "object", we will try to get its property names.
2) If remoteObject.type is "number", with think remoteObject.value is a number

[aandrey, 2013-11-26 16:19:57]

Simplified the patch.
PTAL.

[pfeldman, 2013-12-02 12:10:07]

lgtm

[commit-bot: I haz the power, 2013-12-02 13:36:30]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/aandrey@chromium.org/83383002/110001

[commit-bot: I haz the power, 2013-12-02 15:01:02]

Change committed as 162991