Re: [dom] Need to describe the interaction of adoptNode with prototype chains from Anne van Kesteren on 2012-12-24 (www-dom@w3.org from October to December 2012)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 24 Dec 2012 11:58:46 +0100
To: David Bruant <bruant.d@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, www-dom@w3.org, Cameron McCormack <cam@mcc.id.au>, Bobby Holley <bholley@mozilla.com>
Message-ID: <CADnb78hzxN+snY9y3kPmsv=T-MRWescNqLbv+En2P=_HYBfMFw@mail.gmail.com>

On Mon, Dec 24, 2012 at 11:53 AM, David Bruant <bruant.d@gmail.com> wrote:
> One thing to keep in mind is that in ES6, it won't be possible to change the
> [[Prototype]] of an object with [[Extensible]]:false (it's currently the
> case in Firefox, I haven't tested others).
> It means that nodes (and anything that can have its *associated object*
> changed) must throw on Object.preventExtensions/seal/freeze (I don't know
> what WebIDL currently says about that).

Given the document.open() scenario this might potentially be
everything in the platform... The alternative would be to not garbage
collect the previous Window ever, which would be sad :-(


-- 
http://annevankesteren.nl/

Received on Monday, 24 December 2012 10:59:13 UTC