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

[Bug 20567] Change [[Prototype]] for concept-node-adopt?

From: <bugzilla@jessica.w3.org>
Date: Fri, 18 Oct 2013 01:29:17 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20567-3890-BWkXSsVuWg@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567

--- Comment #45 from Blake Kaplan <mrbkap@gmail.com> ---
There are really no good solutions here.

Ignoring web components for a second, I have a slight preference for changing
the prototype of nodes when they're adopted since that would mean that all
nodes have the exact same interface (so if a page does, e.g.
Element.prototype.operation = ()=>{...}, it can call operation() on any element
in the page without worrying about whether or not 'operation' will be defined).
The leak arguments are also pretty strong, IMO, as well as the fact that, at
least in Gecko, any time we have a cross-global reference, we pay a performance
penalty every time we access the object.

With web components, that gets even more complicated: removing the web
component-added prototype is obviously a non-starter (we might as well detach
the web component binding) and, given that, no matter what we do in this case
will leak the "old" document/window. How important that is, I don't know.

I'm also happy to jump on a call to discuss this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 18 October 2013 01:29:20 UTC

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