W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

Re: Determining what prototype should be used for an object

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Fri, 14 Nov 2014 19:06:10 -0500
Message-ID: <546698F2.4020101@mit.edu>
To: Allen Wirfs-Brock <allen@wirfs-brock.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>, Anne van Kesteren <annevk@annevk.nl>, Ian Hickson <ian@hixie.ch>
On 11/14/14, 2:20 PM, Boris Zbarsky wrote:
> Though maybe we don't want to tie this to [NewObject] and instead just
> say that an object that's created gets created in the current Realm,
> with an opt-out for specs to use the Realm of "this" as needed, and just
> manually adjust things like getContext.

The main issue with this approach is that I suspect it makes creating an 
object much more complicated.  Specifically, it requires that creating 
an object specify that all "built-in" property values on the object that 
are owned by it are created at the same time, using the same Realm as 
the object creation itself (since that's the conceptual model).

This is problematic, since multiple specs can define partial interfaces 
that add new properties to objects...

Maybe we can figure out a way to spec this that's clear, but I haven't 
though of one yet using this approach.

Note that this is also an issue ES doesn't have to worry about.  :(

Received on Saturday, 15 November 2014 00:06:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC