W3C home > Mailing lists > Public > www-dom-ts@w3.org > February 2002

Xerces 2 failure on cdatasectionnormalize

From: Curt Arnold <carnold@houston.rr.com>
Date: Mon, 11 Feb 2002 23:17:58 -0600
Message-ID: <002201c1b384$a5f0ef10$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
Appears to be a bug below in Xerces 2 below the DOM Parser.  When building an element from:
<name>Martha Raynolds<![CDATA[This is a CDATASection with EntityReference number 2 &ent2;]]>
<![CDATA[This is an adjacent CDATASection with a reference to a tab &tab;]]></name>

the element will have the correct number of child nodes (4), a text node containing "Martha Raynolds", a CDATASection node containing "This is ... &ent2;", a text node containing a new line and a last CDATASection.  However, instead of containing "This is... &tab;", it contains "This is ... &ent2;This is .. &tab;"  I assume this is due to a StringBuffer (or comparable) somewhere lower in Xerces that wasn't reset.

We should add additional tests for normalize in the next phase, since the existing tests start out with a loaded document which at least Xerces constructs normalized.  To really test normalize(), you would have to explicitly create an unnormalized document by creating and adding adjacent text nodes or other unnormalized features.
Received on Tuesday, 12 February 2002 00:18:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:04 UTC