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

Re: Issues about the DOM TS brought up in the DOM WG Telcon

From: Curt Arnold <carnold@houston.rr.com>
Date: Wed, 20 Feb 2002 22:34:56 -0600
Message-ID: <00c501c1ba91$1d822fe0$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
> 1. Browser sniffing -- it seems that the sniffing is not elaborate
> enough, makes Mozille, for example, run code with calls to an ActiveX
> object.

I'll admit that it isn't elaborate, but under what scenario does Mozilla run
an ActiveX object?

> 2. Tests on default attributes require a validating parser, which is not
> a requirement (for XML)

It doesn't require that the document be validated, but it does require that
the DTD be processed.  The DOM rec doesn't seem to allow a processor to omit
default attributes or return null for doctype when there is a DTD.

, for HTML default attributes need to be there.
> The issue is then that the TS tests the XML appclication DOM, not the
> browser DOM

The DOM Level 1 test suite currently only contains tests for XML and SVG
documents.  Microsoft IE does not have an browser implementation of the XML
DOM so the MSXML2.DOMDocument is used for tests using XML documents.  Since
Mozilla does have a XML DOM in the browser, it is used for tests on XML
documents.  I believe that Netscape was converting going to be providing DOM
1 Core tests that use HTML documents, and when those tests are run using
HTML documents they will use the browsers HTML DOM implementation.

> And from IBM:
> 1. readonly issues, as indicated in a previous message

Let me search the archives and come up with a history of the discussion on
these tests.

> 2. Ability to run single tests (in Java) instead of the entire suite. I
> promised to come back with relevant info on how not to run entire suites
> (this is the way we run it right now)

From the command line, if you do:

java -classpath dom1-core.jar <testclassname>

such as:

java -classpath dom1-core.jar
org.w3c.domts.level1.core.documentcreatecdatasection

it will run just the specified test twice (once for each configuration).
Individual tests cannot be run (currently) from JUnit GUI's since there are
not junit.framework.TestCase derived classes corresponding to each test.
Received on Wednesday, 20 February 2002 23:35:18 UTC

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