Re: Should Document.cloneNode() work in Level 1? from Don Park on 1998-09-09 (www-dom@w3.org from July to September 1998)

From: Don Park <donpark@quake.net>
Date: Wed, 9 Sep 1998 01:59:26 -0700
To: <www-dom@w3.org>
Message-ID: <000d01bddbd0$2de254d0$2ee044c6@arcot-main>

Alfie,

>The problem with transferNode below is that it assumes that
>the destination node can change the ownerDocument for the
>node, which currently isn't possible between implementations.


Yeah, I realized my forgetfulness right after posting it.  This basically
forces transferNode implementation to always move by copying the content.

However, your suggestion also forces cloning.  The question is, are there
any way to do this without cloning?  Just change the definition of
insertChild/appendChild?

Don

Received on Wednesday, 9 September 1998 05:08:55 UTC