Confusion while implementing the DOM.

Don Park donpark at
Thu Jun 3 02:30:03 BST 1999

> really?
> In, w3c's document, the following statements appear.
>  - this results in all the child nodes of the DocumentFragment being
>     moved to the child list of this node.
> Umm, above "moved" word means what?
>   copy-and-paste or cut-and-paste?

Cut and paste.

> The class that I had developed in java has DocumentFragment Object,
> and this class's publish() method insert this DocumentFragment into
> root Document's any Node. after invoking publish() method,
> is it correct this class's DocumentFragment member has no child nodes?
> or not.

The only purpose of having DocumentFragment in the DOM API is to have
children for adoption via insertChild/appendNode.  It is just a placeholder
for nodes which are 'owned' by a Document but not yet part of the Document

> If the original node's of DocumentFragment remained in
> DocumentFragment
> object, I can change the DocumentFragment's childnode's.

huh?  They are moved, cut-and-pasted, out of the DocumentFragment and into
the target node.

> How Current well-known DOM implementaions handles it?
> especially OpenXML?




xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list