W3C home > Mailing lists > Public > www-archive@w3.org > October 2015

RE: Defining exotic objects in IDL, HTML, or both?

From: Domenic Denicola <d@domenic.me>
Date: Fri, 16 Oct 2015 15:33:31 +0000
To: Boris Zbarsky <bzbarsky@mit.edu>, Anne van Kesteren <annevk@annevk.nl>
CC: Bobby Holley <bholley@mozilla.com>, Cameron McCormack <cam@mcc.id.au>, www-archive <www-archive@w3.org>
Message-ID: <CY1PR0501MB1369B858F88297A2D75F3E90DF3D0@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: Boris Zbarsky [mailto:bzbarsky@mit.edu] 

> So really, UAs just have to make operator=== work as if these were the same object.  I believe abarth indicated that was ok for v8/blink.  It's clearly ok for Gecko, because you have to enter a single compartment to do the === and then you have wrappers into the same compartment, which are in fact the same object.

What is the downside of just using the same WindowProxy and Location objects? They can have internal switches that allow them to redirect their behavior to multiple internal Window/InternalLocation objects depending on the caller. That seems like the only way, spec-wise, to make this work. Otherwise we're going to have to do a willful violation of ES262 with regard to === semantics, if I am understanding correctly.


Received on Friday, 16 October 2015 15:34:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 16 October 2015 15:34:03 UTC