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

Re: [Process] Action items proposal to start using the issue tracker ot Sourceforge

From: Dimitris Dimitriadis <dimitris@ontologicon.com>
Date: Tue, 17 Sep 2002 13:07:45 +0200
Cc: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
To: David Faure <david@mandrakesoft.com>
Message-Id: <B1BB6510-CA2D-11D6-BFEB-000393556882@ontologicon.com>


The only downloadable version of the DOM TS for Level 1 is the one on 
the main DOM TS page which we released a while ago. It could be of help 
as the tests are basically the same; however, you'd need to change the 
JsUnit version to see if it runs in Konqueror.

Later during the day I'll diug throuhg the archives to find latest 
activities and bottlenecks and will ask that people submit their issues 
either to the list or the issue tracker (which is preferrable) so that 
we all can have a fairly goodpicture of where we stand (I've has some 
problems to give a fair report to the DOM WG as not all issues have been 
reported to this list, for example.)


On Tuesday, September 17, 2002, at 12:35  PM, David Faure wrote:

> Hash: SHA1
> On Tuesday 17 September 2002 06:28, Curt Arnold wrote:
>> No current activity.  Will participate in conference call barring 
>> unforseen
>> conflicts.
>> I have been disappointed not to hear anything else from David Faure 
>> from
>> MandrakeSoft.  It would be nice to get Konqueror running the test 
>> suite, but
>> there is something (probably simple) that was blocking my earlier 
>> attempts
>> to run JsUnit.
> Yes it's still on my TODO list to try with saxon instead of xalan ...
> But note that the complexity of the build process for the test suite 
> doesn't
> really help. I have to spend much time debugging Java problems (which I
> don't know much about), when all I want to do is test the Javascript in 
> Konqueror.
> Why not make the generated tests available somewhere? It would be of
> much help if someone could send me a 'built' tarball, with all the tests
> ready to run.
> I'm also waiting for input from the JSUnit developers, I have reported
> problems to them (including a testcase of what JSUnit relies on,
> which doesn't seem to work in any browser? Strange).
> Does anyone know when exactly the onload event for iframes is supposed
> to be emitted? In the testcase below, some browsers (Mozilla IIRC) 
> don't emit it at all,
> some others (IE, IIRC) emit it only during the initial loading of the 
> page...
> but JSUnit relies on it being emitted when load() is called (i.e. when
> the iframe loads some new contents).
> <html>
>   <head>
> <script language="JavaScript">
>   function load(uri)
>   {
>     window.frames.documentBuffer.document.location.href = uri;
>   }
>   function loadComplete()
>   {
>     alert("loadComplete");
>   }
> </script>
> </head>
> <body>
>         <neutered_iframe name="documentBuffer" 
> onload="loadComplete()"></iframe>
>         <p>
>         <a href="javascript:load('empty.html');">Load</a>
>         </p>
> </body>
> </html>
> - --
> David FAURE, david@mandrakesoft.com, faure@kde.org
> http://people.mandrakesoft.com/~david/
> Contributing to: http://www.konqueror.org/, http://www.koffice.org/
> Get the latest KOffice - http://download.kde.org/stable/koffice-1.2/
> Version: GnuPG v1.0.7 (GNU/Linux)
> iD8DBQE9hwV172KcVAmwbhARApzuAJ9V9N4wWqOx/E/dYqVCbSUSpmZUfgCdEkFB
> JECuKWqKckU/QO+NszL4ePc=
> =fL0v
Received on Tuesday, 17 September 2002 07:07:58 UTC

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