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

RE: Another try at injection

From: Jason Brittsan <jasonbri@microsoft.com>
Date: Mon, 11 Feb 2002 11:46:40 -0800
Message-ID: <D5C70EA9DF70694391969A1494875A12031465A3@red-msg-05.redmond.corp.microsoft.com>
To: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Cc: <jsunit@yahoogroups.com>
Using this patch seems to fix the problem.





-----Original Message-----
From: Curt Arnold [mailto:carnold@houston.rr.com] 
Sent: Monday, February 11, 2002 6:59 AM
To: www-dom-ts@w3.org
Cc: jsunit@yahoogroups.com
Subject: Another try at injection


The problem that Jason and Mary were experiencing were probably due to
calling a method, setTracer, that was just injected into the test page
in the previous line of jsUnitRunner.js.  setTracer() is used to pass to
the test a Tracer object that enables the warn, debug and inform


The attached zip files contains replacements for main.html,
jsUnitCore.js and jsUnitRunner.js from the previous patches.  In these
files, instead of the testRunner setting the tracer object, the tests
will retrieve the tracer object from their parent when warn, debug and
inform are called.


warn, debug and inform are not used by the DOM tests, but can be checked
by running the jsUnitTestSuite self-test suite.


Please let me know if this resolves the issue and please confirm that
the self test passes appropriately.




Received on Monday, 11 February 2002 14:47:37 UTC

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