W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

RE: Adopting a Custom Element into Another Document

From: Domenic Denicola <d@domenic.me>
Date: Wed, 14 Jan 2015 15:49:53 +0000
To: Anne van Kesteren <annevk@annevk.nl>
CC: Ryosuke Niwa <rniwa@apple.com>, Webapps WG <public-webapps@w3.org>, "Boris Zbarsky" <bzbarsky@mit.edu>
Message-ID: <CY1PR0501MB1369CA777F70E557E8299419DF410@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: Anne van Kesteren [mailto:annevk@annevk.nl] 

> Because it's very easy to move nodes from one tree to another and this happens quite a bit through <iframe> and such. If the <iframe> then goes away it would be a shame to have to leak it forever. This is all discussed to great extent in the aforementioned bug.

It's no more or less easy than moving normal JS objects from one realm to another, and we don't `__proto__`-munge those.
Received on Wednesday, 14 January 2015 15:50:24 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC