W3C home > Mailing lists > Public > www-dom-ts@w3.org > August 2001

Now passing all tests with "normal" settings with Xerces and close with Crimson

From: Curt Arnold <carnold@houston.rr.com>
Date: Wed, 22 Aug 2001 18:17:49 -0500
Message-ID: <011f01c12b60$a90ed1a0$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
Cc: "Edwin Goei" <edwingo@sun.com>
I've just committed changes to the tests, supporting Java sources, transforms and a minor change to the DTD and schema (ignoringElementContentWhitespace instead of ignoreElementContentWhitespace).   Currently, Xerces-J 1  is passing all tests and Crimson (CVS version) is passing all but three when runnng with default parser settings.

The tests that Crimson is failing are:

documentCreateElementDefaultAttr: Calls document.createAttribute("address") and expects the default attribute from the DTD to be automatically added

documentCreateEntityReferenceKnown: calls document.createEntityReference("ent3") and expects the content model of the entity to be available.

notationGetSystemId: Crimson returns an absolute URL (jar:file://...../notation2File instead of notation2File)

Roughly 45 tests are failing when running with a complementary set of parser settings, I assume primarily due to entity reference expansion.  Since expanding entity references on loading is an acceptible behavior (and the only behavior that some parsers such as Xerces-C support), tests that depend on the presence of entity references must either be declared to be only valid when entity expansion is off or the test must be rewritten to adapt to the settings.
Received on Wednesday, 22 August 2001 19:17:56 UTC

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