Use ScriptPromiseResolverWithContext.

Use ScriptPromiseResolverWithContext.

Use ScriptPromiseResolverWithContext instead of a pair of
ScriptPromiseResolver and NewScriptState.
This CL doen't change the behavior in many cases: The only exception
is when the resolution / rejection happens on the suspended or stopped
ExecutionContext. In such a case, ScriptPromiseResolver suspends or stops
resolution or rejection.

R=ksakamoto@chromium.org
BUG=352552
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=171418

[Kunihiko Sakamoto, 2014-04-14 03:55:32]

lgtm

[yhirano, 2014-04-14 04:23:03]

+haraken for OWNER review

[haraken, 2014-04-14 04:24:41]

LGTM. Thanks for doing this. I'd be happy if you could replace all hand-written
PromiseResolver family with ScriptPromiseResolverWithContext.

[yhirano, 2014-04-14 04:34:08]

On 2014/04/14 04:24:41, haraken wrote:
> LGTM. Thanks for doing this. I'd be happy if you could replace all
hand-written
> PromiseResolver family with ScriptPromiseResolverWithContext.

Yes, I will do. Switching to ScriptPromiseResolverWithContext makes switching to
v8 Promises easier.

[yhirano, 2014-04-14 04:34:12]

The CQ bit was checked by yhirano@chromium.org

[commit-bot: I haz the power, 2014-04-14 04:34:23]

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

[commit-bot: I haz the power, 2014-04-14 05:04:06]

Change committed as 171418