These changes require the newest JsUnit 2.0 beta. See http://dev.bclary.com/ for
the version used. The changes to JsUnit 2.0 have been approved by Edward Hieatt
and will be checked into the CVS Trunk later today. These changes are part of a
number of other changes meant to improve cross browser support in JsUnit/DOM TS
and reduce errors. See http://dom-ts.bclary.com/ for a working version of the
DOM TS with the latest JsUnit 2.0 and these and other changes. 

Note that with the new JsUnit and these changes Opera and Konqueror can run the
DOM TS.

ecmascript/DOMTestCase.js:

Does not support Opera/Konqueror loading data in IFRAMEs due to a DOM 2 only
implementation used in the IFrameBuilder.preload and IFrameBuilder.load methods.

References to potentially undefined properties, e.g.
top.jsUnitParmHash.namespaceaware, are not errors however do flag a warning in
Mozilla in strict mode. In an effort to find and eliminate all errors in JsUnit
and the ECMAScript binding in the DOM TS, I changes all such references in
JsUnit and DOM TS framework to eliminate such warnings.

DOMTestSuite.js:

updateIncompatibleTests is called twice in a row: once in update and potentially
recursively. The recursive call is not required.

alltests.html in each TS currently shows inconsistent choices for
implementations, content type etc. This can be improved by testing for abilities
to use implementations or the availability of specific content types in each TS.