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

Re: Another try at injection

From: Dimitris Dimitriadis <dimitris@ontologicon.com>
Date: Mon, 11 Feb 2002 18:50:31 +0100
Cc: <www-dom-ts@w3.org>, <jsunit@yahoogroups.com>
To: "Curt Arnold" <carnold@houston.rr.com>
Message-Id: <D7549962-1F17-11D6-8164-000393556882@ontologicon.com>
If it works correctly, will we have any licensing issues by bundling?

On Monday, February 11, 2002, at 03:59 , Curt Arnold wrote:

> 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 
> routines.
> 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 12:49:42 UTC

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