gareth 2003/03/03 00:51:53
Modified: c/doc faq-parse.xml
Log:
Fix to docs Bug #13429. Patch from Neil Graham.
Revision Changes Path
1.56 +11 -3 xml-xerces/c/doc/faq-parse.xml
Index: faq-parse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-parse.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- faq-parse.xml 5 Feb 2003 18:56:00 -0000 1.55
+++ faq-parse.xml 3 Mar 2003 08:51:52 -0000 1.56
@@ -360,10 +360,18 @@
</a>
</faq>
- <faq title="Why DOMNode::cloneNode() does not clone the pointer assigned to a
DOMNode via DOMNode::setUserData()?">
- <q>Why DOMNode::cloneNode() does not clone the pointer assigned to a DOMNode
via DOMNode::setUserData()?</q>
+ <faq title="Why does DOMNode::cloneNode() not clone the pointer assigned to a
DOMNode via DOMNode::setUserData()?">
+ <q>Why does DOMNode::cloneNode() not clone the pointer assigned to a DOMNode
via DOMNode::setUserData()?</q>
<a>
- <p>&XercesCName; supports the DOMNode::userData specified in
+ <p>&XercesCName; supports the DOMNode::userData specified
+ in <jump
href="http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030226/DOM3-Core.html#core-ID-3A0ED0A4";>
+ the DOM level 3 Node interface</jump>. As
+ is made clear in the description of the behaviour of
+ <code>cloneNode()</code>, userData that has been set on the
+ Node is not cloned. Thus, if the userData is to be copied
+ to the new Node, this copy must be effected manually.
+ Note further that the operation of <code>importNode()</code>
+ is specified similarly.
</p>
</a>
</faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
