- From: Curt Arnold <carnold@houston.rr.com>
- Date: Tue, 23 Sep 2003 00:18:46 -0500
- To: www-dom-ts@w3.org
Philippe Le Hegaret wrote: >FYI, Peter found a few bugs with the DOM Level 1 tests/framework: >http://www.w3.org/Bugs/Public/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=DOM+TS&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop >If someone can have a look at them, that would be nice, > >Philippe > > > > > I've closed all three bugs as fixed. One was a stray attribute in the build.xml file, another was an description that was not consistent with the body of the the test. The third bug, http://www.w3.org/Bugs/Public/show_bug.cgi?id=261, involved hc_nodeinsertbefore.xml which was a transliteration of the XML-specific test nodeinsertnode.xml. The setup of the test depended on the preservation of the whitespace between the p and em elements in the following fragment: <p> <em>EMP0002</em> XML processors and Mozilla's HTML implementation would preserve the whitespace node, Konqueror and IE would eliminate the whitespace node. I've changed the test so it not affected by elimination of the whitespace node. If eliminating the whitespace node should be considered non-conformant, then a distinct test should be written to check for the behavior. However, it would appear to be a reasonable application-specific optimization of the content.
Received on Tuesday, 23 September 2003 01:18:48 UTC