- From: Curt Arnold <carnold@houston.rr.com>
- Date: Mon, 8 Apr 2002 16:25:28 -0500
- To: "Rick Rivello" <richard.rivello@nist.gov>
- Cc: <www-dom-ts@w3.org>
> Curt can I also take the same approach with the html_alltests.html file > so that I can run the tests on IE? I'm not sure what is going on when you are running the tests on IE. > Here are the results > > 3. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLAppletElement05 > failed > > "codeBaseLink" > Expected ./files/ (string) but was http://xw2k.sdct.itl.nist.gov/brady/dom/files/ (string) I believe both IE and Mozilla return absolute URI's for the HTMLApplet.codebase attribute. The text doesn't explicitly prohibit or require returning an absolute URI. I added an <assertURIEquals> element into the DOM TS language for such a case, but I don't believe that is has been used yet and not sure if the supporting code is implemented. > > 10. > file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLButtonElement01 > failed > > "formLink" > Expected form2 (string) but was (string) HTMLFormElement.name does not specify what connection this property accessor has with the [X]HTML content. <form> does not have a name attribute defined. The test expects that value of the id attribute to be returned. > > 15. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLElement01 > failed > > "idLink" > Expected Test-HEAD (string) but was (string) > > 16. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLElement30 > failed > > "titleLink" > Expected HEAD Element (string) but was (string) > > 17. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLElement59 > failed > > "langLink" > Expected en (string) but was (string) > > 18. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLElement88 > failed > > "dirLink" > Expected ltr (string) but was (string) > > 19. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLElement117 > failed > > "classNameLink" > Expected HEAD-class (string) but was (string) All tests look like a problem with the class created for the <head> element in the implementation. Similar tests on other elements seem to work fine. > 21. > file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLFieldSetElement01 > failed > > "formLink" > Expected form2 (string) but was (string) Same issue as test 10 > > 24. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLFormElement03 > failed > > "nameLink" > Expected form1 (string) but was (string) Same issue as test 10 > > 29. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLHtmlElement01 > failed > > "versionLink" > Expected transitional 4.0 (string) but was transitional xhtml 1.0 (string) The content of the version attribute of the html element differ between html.html and html.xml. Would be better if html.html and html.xml both contained the same version attribute. > > 32. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLInputElement08 > failed > > "checkedLink" > Call to assertTrue(boolean) with false Looks like an implementation bug. "checked" is the only legal value for the checked attribute in XHTML 1.0's DTD. I assume that the implementation didn't check for that value and just passed the attribute value to a boolean conversion routine. > > 34. > file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLIsIndexElement01 > had an error > > Error message is: > "TypeError: fNode has no properties" Looks like an implementation problem, but if fixed would run into the issue from test #10. > > 39. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLLinkElement01 > failed > > "disabledLink" > Call to assertTrue(boolean) with false Looks like similar implementation problem to test #32 > > 58. > file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/e cmascript/tests/alltests.html:testHTMLTableRowElement07 > failed > > "bgColorLink" > Expected #00FFFF (string) but was #00ffff (string) The corresponding .xml document isn't valid XHTML as the bgcolor element has been deprecated. The HTML DOM spec isn't clear if the bgcolor should reflect the color as implied by a stylesheet or only an explicit bgcolor attribute. It would be good if you could test the test documents against the W3C XHTML and HTML validation service. Got to run.
Received on Monday, 8 April 2002 17:26:06 UTC