Bindings: Support [ConstructorCallWith=ScriptState]

Bindings: Support [ConstructorCallWith=ScriptState]

Sometimes an ExecutionContext just isn't enough.

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

[jsbell, 2014-12-05 20:09:44]

jsbell@chromium.org changed reviewers:
+ haraken@chromium.org, jl@opera.com

[jsbell, 2014-12-05 20:09:45]

haraken@, jl@ - please take a look?

The specific use case is crrev.com/779133003 (which is not ready to land, lots
of work remaining). A constructor kicks off an asynchronous operation, which
eventually results in a promise being resolved. This could be done other ways,
but this seemed clean and ScriptState is awesome.

[Jens Widell, 2014-12-05 20:34:33]

LGTM

[jsbell, 2014-12-05 21:07:38]

The CQ bit was checked by jsbell@chromium.org

[commit-bot: I haz the power, 2014-12-05 21:08:22]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/741783003/1

[commit-bot: I haz the power, 2014-12-05 21:14:10]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=186624

[haraken, 2014-12-06 01:28:41]

https://codereview.chromium.org/741783003/diff/1/Source/bindings/IDLExtendedA...
File Source/bindings/IDLExtendedAttributes.txt (right):

https://codereview.chromium.org/741783003/diff/1/Source/bindings/IDLExtendedA...
Source/bindings/IDLExtendedAttributes.txt:45:
ConstructorCallWith=ExecutionContext|ScriptState|Document

Can we probably remove ExecutionContext and Document? We can get an
ExecutionContext and a Document from a ScriptState.

(This might not be easy. I remember jl@ did some work to remove
ExecutionContext, but we decided not to land the CL because we had to introduce
C++ constructors that take a Document argument, which slightly mess up core/
code.)

[haraken, 2014-12-06 01:29:00]

LGTM