Confusion while implementing the DOM.
donpark at quake.net
Wed Jun 2 20:33:00 BST 1999
> Andrew Douglas wrote,
> > The standard I've got states that a DocumentFragment is
> > a Node (or at least, it does in the Java headers I've
> > got). That was my mistake, I think.
> No mistake. A DocumentFragment *is* a Node. But if you
> try and insert it into the tree, you'll find that a
> conforming implementation will throw a
Actually, inserting a DocumentFragment 'node' into a tree should insert the
child nodes of the DocumentFragment (leaving it empty).
HERARCHY_REQUEST_ERR exception should be thrown only if any of the child
nodes can not be inserted. State of the tree after partially sucessful
DocumentFragment insertion is unspecified in the spec. My implementation
revokes the entire operation leaving the tree and the DocumentFragment
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev