[whatwg] global object in onmessage event? Really?

Section 9.2.3, step 5 reads:

> Create an event that uses the MessageEvent interface, with the event name message, which does not bubble, is not cancelable, and has no default action. The data attribute must be set to the value of message clone, the origin attribute must be set to the Unicode serialization of the origin of the script that invoked the method, and the source attribute must be set to the script's global object.

Is the source property really supposed to be the global object and not 
the WindowProxy object?  I thought that the point of WindowProxy was 
that you were *never* supposed to be able to obtain a reference to the 
real global object.

     David Flanagan

Received on Saturday, 13 February 2010 14:26:50 UTC