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

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Feb 2014 20:07:31 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20567-3890-tqxf8UT9IF@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567

--- Comment #69 from Dimitri Glazkov <dglazkov@chromium.org> ---
Just a quick update: a bunch of Mozilla and Google folk chewed some more on the
problem and reached a conclusion that we can avoid solving this problem for
custom elements for now.

1) Anne presented the fact that we will need "adopt" callback for custom
elements to adjust baseURL when a node is adopted into a document. The same
callback could be used (as a UA implementation detail) to swizzle prototypes
for engines that do want to change the prototype and do nothing for engines
that don't.

2) The adopt callback will accept two arguments: old document and new document.

3) A new registry API will need to exist to expose the "registry" concept in
the current custom elements spec:
http://w3c.github.io/webcomponents/spec/custom/#dfn-registry. This registry
will be exposed as a member of a Document object and allow the adopt callback
reason about what to do with the element definitions across documents. The
registry will likely look like a map of definitions.

I will take an action item to work on the registry spec and refactor custom
elements spec to depend on it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 6 February 2014 20:07:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:51 UTC