[Bug 27420] [Custom]: need a hook for transfering data while cloning elements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27420

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> ---
> and then HTML should specify the clonedCallback behavior

There's a timing difference here, right?  The current cloning steps behavior
means there are never script-exposed elements that don't have the relevant
state propagated yet, while using clonedCallback for this would mean there are.

Whether this is a problem in practice probably depends on the element.  For
example, for a <script> the cloning steps are what propagates the "don't
execute again" flag, so this change would allow a single <script> element to
execute multiple times...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 24 November 2014 17:53:32 UTC