Re: Determining what prototype should be used for an object from Boris Zbarsky on 2014-11-17 (public-script-coord@w3.org from October to December 2014)

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Mon, 17 Nov 2014 10:47:51 -0500
To: Anne van Kesteren <annevk@annevk.nl>
CC: Allen Wirfs-Brock <allen@wirfs-brock.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Ian Hickson <ian@hixie.ch>
Message-ID: <546A18A7.2090403@mit.edu>

On 11/17/14, 10:39 AM, Anne van Kesteren wrote:
> On Mon, Nov 17, 2014 at 4:29 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> That being to have the non-ES behavior of using the "this" object to
>> determine the Realm, yes?
>
> Yeah, if we keep that we'd have to define that somehow. It will become
> weird of course if objects move into becoming ES library objects over
> time. See ArrayBuffer and friends, promises in Gecko.

Yep.  I bet if you Promise.prototype.then.call on a Promise from another 
global, what Gecko has right now doesn't follow the ES spec.

-Boris

Received on Monday, 17 November 2014 15:48:22 UTC