This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24577 - [Custom]: Need adopted callback
Summary: [Custom]: Need adopted callback
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968 20567
  Show dependency treegraph
 
Reported: 2014-02-07 10:45 UTC by Anne
Modified: 2015-07-06 08:15 UTC (History)
2 users (show)

See Also:


Attachments

Description Anne 2014-02-07 10:45:19 UTC
See bug 20567 comment 69. We should have a callback for adoption so you can deal with moving to a new document and prevent leaking an entire global. The callback should take the old and new document as arguments.

See bug 24570 for the equivalent bug on cloning.
Comment 1 Anne 2014-02-10 10:54:39 UTC
New document is not needed as argument since you can get the node's ownerDocument (its node document).
Comment 2 Anne 2014-02-10 11:13:20 UTC
If you cannot model this after http://dom.spec.whatwg.org/#concept-node-adopt-ext please tell me.
Comment 3 Anne 2014-02-10 11:13:46 UTC
Obviously that callback in the DOM will need to be made asynchronous. Will do that once there's a proper hook in IDL or some such.
Comment 4 Hayato Ito 2015-07-06 08:15:04 UTC
Moved to https://github.com/w3c/webcomponents/issues/210