[whatwg] cloneNode and HTML elements

Robert O'Callahan robert at ocallahan.org
Thu Sep 10 02:30:49 PDT 2009

On Thu, Sep 10, 2009 at 8:13 PM, Jonas Sicking <jonas at sicking.cc> wrote:

> My assumption was always the opposite. For example for <input>
> elements we clone the 'value' API attribute, as well as the internal
> has-changed-value bit (used for form field restore when going back to
> a page).

Looks like Opera and Webkit clone some form control state too (the text of
text inputs, at least). Haven't tested IE, but it seems likely that
interoperability requires at least some cloning of hidden state, so this
does need to be specified somewhere.

I don't particular care what the spec ends up being. For media elements,
cloning some hidden state could be useful, but it is hard to implement.

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090910/db1a6aa4/attachment-0002.htm>

More information about the whatwg mailing list