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

Re: dom1-core-jar works (was: Re: Build failed (dom1-core-jar))

From: Dimitris Dimitriadis <dimitris@ontologicon.com>
Date: Wed, 6 Feb 2002 00:37:15 +0100
Cc: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
Message-Id: <494EEDE3-1A91-11D6-94E3-000393556882@ontologicon.com>
comments inlined

On Tuesday, February 5, 2002, at 11:39 , Arnold, Curt wrote:

>> I'd like us to take some kind of decision on how long to wait for input
>> from Edward. So far, we've aimed at the end of January, beginning of
>> February at the latest for releasing the DOM Level 1 Core TS.  I'd like
>> for us not to end up too far from that.
>
> So far it has been about 72 hours.  The patch did reach the JSUnit 
> mailing
> list and I sent it to edward@jsunit.net, however it would be nice to 
> email a
> more direct email address in case there is a forwarding problem.  I'll 
> try
> to find one tonight.
>
> Given the audience, I don't think adding the Doxygen documentation will
> prove to be a bandwidth burden and I would lean toward 2, though it 
> would be
> nice to know how much the Doxygen documentation adds to the archive 
> size.
>
[dd] We'll know pretty soon, I hope to be able to finalize the matrix 
XSLT (basically to simplify reading and allow linking to tests (locally) 
as well as print out test purpose in table form before it gets too late) 
as well as zip the entire distribution. I'll post results later, 
tomorrow morning at the latest (GMT +1)

> 1: 0
> 2: [dd] 1, [ca] 0.8
> 3: 0
> 4: 0
>
>
> The "logic" (if you could call it that) that detects whether Mozilla has
> completed loading an XML document appears to be broken.  Basically, 
> there is
> a loop in DOMTestCase.js that checks if the document element tag name 
> has
> changed from a bogus initial value and if it has not then it puts up an
> alert() box to stall for time.  With Mozilla 0.9.8, the document 
> element tag
> name does not change within the loop and so it will put up the maximum
> number of alert boxes (5) per load attempt.  However, the document 
> appears
> to be ready almost immediately.  I'm going to change the maximum number 
> of
> alert boxes to 1 which will significantly reduce the pain of running the
> Mozilla tests.
> Has anyone tried running the JSUnit tests on the web?
[dd] No, even if I'm thinking of running them that way if it solves my 
problem of it (still) not working on my OSX machine; problems with the 
path. However, if I'm the only one experienceing problems with JsUnit, 
let's not spend more time on changing the code and instead hope that 
Edward replies soon.
Received on Tuesday, 5 February 2002 18:36:33 UTC

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