Re: New JS Body attributes

Can someone remove me from this mailing list?

 

- Peter

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of Wolfgang Fahl
Sent: Tuesday, April 01, 2008 10:11 AM
To: Discussion of use and development of HttpUnit
Subject: Re: [Httpunit-develop] New JS Body attributes

 

Mark wrote: 

> I am working on getting FormScriptingTest to run with the new DOM. 

> Currently, I am working on testGetAttributeForBody(). Firstly, lines 

> 112-114 should read: 

> 

>  String expected[]={ 

>  "#FFFFCC","#E00000","#0000E0","#000080","#000000" 

>  }; 

> The test values that are there now do not match the attributes. 

That's my fault - I could not test it so the copy/paste was probably not o.k. svn 873 has your version. 

> Secondly, I find that in ScriptFilter.startElement( QName element, 

> XMLAttributes attrs, Augmentations augs ), for the body element, attrs 

> contains no actual data, just a bunch of nulls. For the form element in 

> FormScriptingTest.testFormNameProperty(), attrs contains the name, as 

> one would expect. If I modify the show() javascript function in 

> testGetAttributeForBody() to explicitly set the body attributes (eg, 

> body.bgcolor='#FFFFCC'), then the test passes correctly. 

> 

> I conclude that the body attributes are not being set correctly when the 

> element is initialized. This problem is occurring in either Xerces or 

> Neko. The jars which come with the httpUnit-1.6.2 distribution don't 

> have line number references or attached source, so debugging is 

> impractical. 

> 

> Does anybody know of a set of Neko and Xerces jars which a) work with 

> the current build of httpUnit, and b) come with source and compiled line 

> numbers? 

I have changed my Eclipse configuration to use 

Xerces-J-src.2.6.1.zip from the Apache web site. 

 

and debugging works better with that. 

 

Please check whether my refactoring is compatible with yours so far as of 873. Especially the clickSequence handling is something I'm afraid needs to be handle better. Just imagine an onmousedown or onmouseup event enabling or removing a button or clickable element or such - I believe these things can get pretty nasty and I wonder how the browsers out there are really common in their behaviour for such (may be broken) Javascript code. 

 

Wolfgang 

 

BITPlan - smart solutions 

Pater-Delp-Str. 1, D-47877 Willich Schiefbahn 

Tel. +49 1805 - BITPLAN / +49 1805 248 752, Fax +49 2154 811-481 

Web: http://www.bitplan.de 

bitplan GmbH, Willich - HRB 6820 Krefeld, VAT-ID: 10258040548, Geschäftsführer: Wolfgang Fahl

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
Httpunit-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/httpunit-develop