Expose WorkerGlobalScope interface in worker environment

Expose WorkerGlobalScope interface in worker environment

Expose WorkerGlobalScope interface in worker environment as per the latest
specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#the-workerglobalscope-common-interface

Also expose the SharedWorkerGlobalScope interface when the JavaScript global environment is a
shared worker environment, and the DedicatedWorkerGlobalScope interface when the JavaScript
global environment is a dedicated worker environment:
http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#sharedworkerglobalscope
http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#dedicatedworkerglobalscope

Split webexposed/global-constructors-listing-worker.html test case into 2 tests (for shared
and dedicated workers) to validate the change.

The semantics of the [GlobalContext] IDL extended attribute has changed to support this
use case. The value for the extended attribute is now the name of the interface to which the
Constructor attribute should be added (Window, WorkerGlobalScope, SharedWorkerGlobalScope...).
It is possible to specify several interface names by using '&' as separator. For e.g.
[GlobalContext=Window&WorkerGlobalScope].

BUG=253473
R=haraken@chromium.org

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

[haraken, 2013-06-26 08:34:08]

LGTM

BTW, current Blink IDL files use '|' (instead of '&') to specify multiple
values. For example, [CallWith=ScriptState|ScriptExecutionContext] means that we
should call a C++ method with ScriptState *and* (Note: this is not *or*)
ScriptExecutionContext. This is confusing. Please consider replacing existing
'|' with '&' in a follow-up CL.

[commit-bot: I haz the power, 2013-06-26 09:44:24]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@sisa.samsung.com/17826003/3001

[do-not-use, 2013-06-26 09:54:01]

On 2013/06/26 08:34:08, haraken wrote:
> LGTM
> 
> BTW, current Blink IDL files use '|' (instead of '&') to specify multiple
> values. For example, [CallWith=ScriptState|ScriptExecutionContext] means that
we
> should call a C++ method with ScriptState *and* (Note: this is not *or*)
> ScriptExecutionContext. This is confusing. Please consider replacing existing
> '|' with '&' in a follow-up CL.

Good idea, I'm on it :)

[commit-bot: I haz the power, 2013-06-26 09:54:56]

Retried try job too often on blink_presubmit for step(s) presubmit
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=blink_pres...

[do-not-use, 2013-06-26 14:08:44]

Committed patchset #2 manually as r153070 (presubmit successful).

[arv (Not doing code reviews), 2013-06-26 14:16:57]

LGTM