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

Re: How should text be normalized for tests?

From: Rick Rivello <richard.rivello@nist.gov>
Date: Mon, 25 Mar 2002 14:26:29 -0500
Message-ID: <12ae01c1d432$f6a7cd10$573b0681@sdct.nist.gov>
To: "Michael B. Allen" <mballen@erols.com>, <www-dom-ts@w3.org>
Michael

   I'm trying to get a better understanding of your problem.

   I wrote the nodegetfirstchildnull test and want to make sure there
   is not a problem with the test.  Is there any way you can send me
   the values of the employeeList.items(0,1,etc). 

Thanks
Rick Rivello




----- Original Message ----- 
From: "Michael B. Allen" <mballen@erols.com>
To: <www-dom-ts@w3.org>
Sent: Monday, March 25, 2002 1:02 AM
Subject: How should text be normalized for tests?


> Expat returns separate #text fragments for newlines and space. This
> results in extra text nodes in my average DOM tree (unless normalize()
> is called of-course). I believe this is acceptable but the
> nodegetfirstchildnull test assumes that the second node is employeeId:
> 
> 67       doc = load("staff");
> 68       elementList = doc.getElementsByTagName("employee");
> 69       employeeNode = elementList.item(0);
> 70       employeeList = employeeNode.getChildNodes();
> 71 --->  secondChildNode = employeeList.item(1);
> 
> This is a #text node for me.
> 
> -- 
> May The Source be with you.
> 
> 
Received on Monday, 25 March 2002 14:27:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:46 GMT