Delete WorldContextHandle in favor of DOMWrapperWorld

Delete WorldContextHandle in favor of DOMWrapperWorld

This updates the last callers of WorldContextHandle: EventListeners.

It also changes DOMWrapperWorld::current() to determine whether it's
operating in a worker or a document context using WrapperTypeInfo
on the v8::Context instead of taking a ScriptExecutionContext (since
some callers don't have one available).

R=abarth
BUG=230460
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=148670

[haraken, 2013-04-18 02:11:52]

Looks great to me, but abarth should look.

[abarth-chromium, 2013-04-18 05:41:51]

LGTM!!!

https://codereview.chromium.org/14334002/diff/1/Source/bindings/v8/DOMWrapper...
File Source/bindings/v8/DOMWrapperWorld.cpp (right):

https://codereview.chromium.org/14334002/diff/1/Source/bindings/v8/DOMWrapper...
Source/bindings/v8/DOMWrapperWorld.cpp:72: if
(!V8DOMWrapper::isWrapperOfType(toInnerGlobalObject(context),
&V8DOMWindow::info))
toInnerGlobalObject can be slow, but I don't think this function is hot enough
for it to matter.

[adamk, 2013-04-18 16:09:24]

On 2013/04/18 05:41:51, abarth wrote:
> LGTM!!!
> 
>
https://codereview.chromium.org/14334002/diff/1/Source/bindings/v8/DOMWrapper...
> File Source/bindings/v8/DOMWrapperWorld.cpp (right):
> 
>
https://codereview.chromium.org/14334002/diff/1/Source/bindings/v8/DOMWrapper...
> Source/bindings/v8/DOMWrapperWorld.cpp:72: if
> (!V8DOMWrapper::isWrapperOfType(toInnerGlobalObject(context),
> &V8DOMWindow::info))
> toInnerGlobalObject can be slow, but I don't think this function is hot enough
> for it to matter.

How slow? There's one sorta-hot example I can think of, which is
requestAnimationFrame, where a new Callback object needs to be created on each
call, and requestAnimationFrame itself is called inside the code that's running
the animation.

[abarth-chromium, 2013-04-18 16:12:26]

On 2013/04/18 16:09:24, adamk wrote:
> How slow?

Roughly the cost of a hash-table lookup.

[adamk, 2013-04-18 17:05:02]

On 2013/04/18 16:12:26, abarth wrote:
> On 2013/04/18 16:09:24, adamk wrote:
> > How slow?
> 
> Roughly the cost of a hash-table lookup.

That seems ok for the use case, I'm going to cq+ this.

[commit-bot: I haz the power, 2013-04-18 17:05:20]

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

[commit-bot: I haz the power, 2013-04-18 17:36:11]

Change committed as 148670