1.x branch please.
----- Message d'origine ----
De : Peter Mularien <[EMAIL PROTECTED]>
À : Usage problems for JWebUnit <jwebunit-users@lists.sourceforge.net>
Envoyé le : Mardi, 23 Janvier 2007, 20h58mn 38s
Objet : Re: [JWebUnit-users] Re : Use of form element name vs. id in API
<!--
_filtered {
margin:1.0in 1.25in 1.0in 1.25in;}
_filtered {font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.emailstyle17
{font-family:Arial;
color:windowtext;}
span.EmailStyle19
{
font-family:Arial;
color:navy;}
_filtered {
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{}
-->
Sounds good. Im a little unclear where
the appropriate place to patch this would be it looks like theres
active development on both the 1.4 and 2.0 branches any preference?
Peter
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Julien HENRY
Sent: Tuesday, January 23, 2007
2:40 PM
To: Usage problems for JWebUnit
Subject: [JWebUnit-users] Re : Use
of form element name vs. id in API
Hi Peter,
No, it's a long awaited feature request. It will be great if you could provide
a patch for this.
FYI :
http://sourceforge.net/tracker/index.php?func=detail&aid=1022916&group_id=61302&atid=497985
++
Julien
----- Message d'origine
----
De : Peter Mularien <[EMAIL PROTECTED]>
À : jWebUnit-users <jwebunit-users@lists.sourceforge.net>
Envoyé le : Mardi, 23 Janvier 2007, 17h27mn 45s
Objet : [JWebUnit-users] Use of form element name vs. id in API
Hi jWebUnit folks,
Is there a reason why the jWebUnit API dealing with form
fields doesnt take name or id, instead of simply name, when referring to
a form element? It seems that some of the API does support name or
id, such as setWorkingForm, goto/hasFrame, get/hasTable, etc; however
this doesnt extend to other APIs where identification of a single
element would be much easier if one could specify an id specifically
setTextField, although there are other examples where this would be useful.
If this was a conscious decision, Id be interested in
the reason for it. If people would find this a useful modification, Id
be happy to volunteer some patches that would allow this to happen. In my use
of jWebUnit, we sometimes cant easily get the name attribute for a form
element, but can always get form elements by id.
Thanks,
Peter
This e-mail and any files transmitted with it are confidential and are intended
solely for the use of the individual or entity to whom they are addressed.
This communication may contain information that is protected from disclosure by
applicable law. If you are not the intended recipient, or the employee or
agent responsible for delivering this communication to the intended recipient,
be advised that you have received this e-mail in error and any use,
dissemination, forwarding, printing or copying of this e-mail is strictly
prohibited. If you believe that you have received this e-mail in error, please
immediately notify Edgewater Technology by telephone at (781) 246-3343 and
delete the communication from all e-mail files.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
JWebUnit-users mailing list
JWebUnit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions ! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo!
Questions/Réponses.
This e-mail and any files transmitted with it are confidential and are intended
solely for the use of the individual or entity to whom they are addressed.
This communication may contain information that is protected from disclosure by
applicable law. If you are not the intended recipient, or the employee or
agent responsible for delivering this communication to the intended recipient,
be advised that you have received this e-mail in error and any use,
dissemination, forwarding, printing or copying of this e-mail is strictly
prohibited. If you believe that you have received this e-mail in error, please
immediately notify Edgewater Technology by telephone at (781) 246-3343 and
delete the communication from all e-mail files.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
JWebUnit-users mailing list
JWebUnit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses
http://fr.answers.yahoo.com-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
JWebUnit-users mailing list
JWebUnit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
