Re: [XHR] Constructor behavior seems to be underdefined

Cameron McCormack:
>>> Would it make sense to require objects that are returned from a
>>> constructor be associated with the same global that the constructor
>>> itself is?

Boris Zbarsky:
>> That seems like the simplest approach to me, yes.  It's what Gecko does in
>> practice anyway at the moment, afaict.

Adam Barth:
> Note: WebKit has bugs in this regard, but we've been (slowly!)
> converging towards Gecko's behavior, which we believe is aesthetically
> correct.

OK, I've made this change.

http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.519;r2=1.520;f=h

Received on Monday, 9 April 2012 08:00:43 UTC