Looks like a bug to me. If you file a JIRA-issue for it, I'll have a closer look
> -----Original Message----- > From: #Cyrille37# [mailto:[EMAIL PROTECTED] > Sent: Monday, July 23, 2007 12:31 PM > To: users@tapestry.apache.org > Subject: Re: [T4.1.2] Is there Client side validation for > @RadioGroup ? > > #Cyrille37# a écrit : > > #Cyrille37# a écrit : > >> For the TextField the client-side validation works, but for > >> @RadioGroup only the server-side validation is called, no > client-side > >> event occured. > > For precision here is following the code at the end of the > generated > > html page. > > > > In that code we can see that there is some > client-side-validation for > > the @TextField "text01" and for the @RadioGroup "radioGroup01". > > But when submiting the form the client-side-validation for > "text01" is > > triggered, but none for "radioGroup01". > > > > <script type="text/javascript"><!-- > > dojo.addOnLoad(function(e) { > > dojo.require("tapestry.form");tapestry.form.registerForm("theForm"); > > tapestry.form.focusField('text01'); > > tapestry.form.clearProfiles('theForm'); > > tapestry.form.registerProfile('theForm', > > {"required":["text01","radioGroup01"], > > "text01":{"required":["Vous devez entrer une valeur pour Le Text > > 01."]}, "radioGroup01":{"required":["Vous devez entrer une > valeur pour > > Le RadioGroup 01."]} });}); // --></script> > > The @RadioGroup makes @Radio got the same "name" attribute > but unique "id" attribute. > Perhaps we have to hack tapestry.form.validation to get > client-side validation working ?? > > Any tips or idea about that ? > Cyrille > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
