- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Oct 2012 23:57:59 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18672
Rafael Weinstein <rafaelw@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from Rafael Weinstein <rafaelw@chromium.org> 2012-10-03 23:57:58 UTC ---
Elliot added the commentary that there is an assumption with cloneNode(true)
that the result is "dead" (e.g. event listeners are gone, canvas's are empty,
etc...). I think not cloning or referencing the content of the original is
consistent with this.
I've removed any discussion of the behavior of cloneNode, thus the existing
cloneNode algorithm will (by default) not operate on the content attribute (and
the clone will initialize itself with an empty document fragment when
referenced).
http://dvcs.w3.org/hg/webcomponents/rev/91b77f44e7d8
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 3 October 2012 23:58:00 UTC