Bindings: rename |resultValue| => |jsValue|

Bindings: rename |resultValue| => |jsValue|

Fixes irregular naming in [ReflectOnly], simplifies code.
Fixes 2 FIXMEs.

BUG=345503
TBR=haraken

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

[Nils Barth (inactive), 2014-03-27 02:54:41]

The CQ bit was checked by nbarth@chromium.org

[commit-bot: I haz the power, 2014-03-27 02:54:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nbarth@chromium.org/212593008/1

[haraken, 2014-03-27 02:55:45]

We're mixing |jsValue| and |v8Value| as well. I think we should unify them to
|v8Value|.

[Nils Barth (inactive), 2014-03-27 02:58:19]

On 2014/03/27 02:55:45, haraken wrote:
> We're mixing |jsValue| and |v8Value| as well. I think we should unify them to
> |v8Value|.

We don't use |v8Value| in generated bindings code,
but we do use |v8_value| in Python.
Will rename so |v8Value| aligns with |v8_value|.

[commit-bot: I haz the power, 2014-03-27 03:56:42]

Change committed as 170128

[Nils Barth (inactive), 2014-03-27 04:06:12]

BTW, is this LGTY?

[haraken, 2014-03-27 04:19:55]

On 2014/03/27 04:06:12, Nils Barth wrote:
> BTW, is this LGTY?

LGTM if you rename |jsValue| to |v8Value| in a follow-up :)

[Nils Barth (inactive), 2014-03-27 05:28:48]

On 2014/03/27 04:19:55, haraken wrote:
> On 2014/03/27 04:06:12, Nils Barth wrote:
> > BTW, is this LGTY?
> 
> LGTM if you rename |jsValue| to |v8Value| in a follow-up :)

Done!
Bindings: rename |jsValue| => |v8Value|
https://codereview.chromium.org/214283002/