- From: Philip TAYLOR <P.Taylor@Rhul.Ac.Uk>
- Date: Fri, 28 Jan 2005 16:26:30 +0000
- To: www-validator@w3.org
- CC: Jaffe <jaffer@earthlink.net>
Hmmm, just a few fragments from the code of the page
cited should provide an indication of the source of
the problems ...
try {
var doc = this._createdoc("2.5", "Microsoft.XMLDOM");
var doc26 = this._createdoc("2.6", "MSXML2.DOMDocument.2.6");
var doc30 = this._createdoc("3.0", "MSXML2.DOMDocument.3.0");
// Check to see if 3.0 sp1 is installed
this._checkfor30sp1(doc30);
var doc40 = this._createdoc("4.0", "MSXML2.DOMDocument.4.0");
}
catch (e) {
this._log("Error: " + e.description);
}
...
var doc = new ActiveXObject(progId);
...
// There were a lot of bug fixes in version 3.0 sp1
// so we want to see if that has been installed.
// Check the KB article Q290988 which describes this
// test.
...
// At this point, we know the version, but we need to find out
// if we are in replace mode. That is, see if the old ProgID
// Microsoft.XMLDOM is really one of the newer MSXML2+ references.
// Version 2.6+ introduced a new property called .namespaces, so
// check to see if it exists in old doc. Since xmlinst did not
// exist until version 3, we can safely assume that if this test
// passes, then the user has version 3 in replace mode.
....
<td>MATERIALS FOR GOVERNMENTAL DELIBERATIVE AND EXECUTIVE DECISION-MAKING PROCESS PRIVILEGED AND CONFIDENTIAL</td>
But only for Govermental servants willing to toe the (MS) party line !
Received on Friday, 28 January 2005 16:29:00 UTC