W3C home > Mailing lists > Public > www-dom@w3.org > July to September 1998

Re: Should Document.cloneNode() work in Level 1?

From: Ray Whitmer <ray@imall.com>
Date: Wed, 09 Sep 1998 10:03:20 -0600
Message-ID: <35F6A6C8.328438EF@imall.com>
To: www-dom@w3.org
Don Park wrote:

> 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?

The point is that an implementation which is transferring a node of an
implementation it recognizes can do whatever it wants beyond the public APIs
to change ownerDocument.  It is only immutable through current public APIs.

But I will clone in any case, because that is more efficient in my
implementation.

Ray Whitmer
ray@imall.com
Received on Wednesday, 9 September 1998 12:03:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:45 GMT