[richfaces-issues] [JBoss JIRA] Issue Comment Edited: (RF-11246) rich:calendar client side validation doesn't work reliable

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620495#comment-12620495 ] 

Brian Leathem edited comment on RF-11246 at 8/11/11 1:05 PM:
-------------------------------------------------------------

Might be worth looking at these calendar issues together (RF-10821)

      was (Author: bleathem):
    Look at these calendar validation issues together
  
> rich:calendar client side validation doesn't work reliable
> ----------------------------------------------------------
>
>                 Key: RF-11246
>                 URL: https://issues.jboss.org/browse/RF-11246
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>         Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9
> Metamer 4.1.0.20110805-M1 r.22604
> Apache MyFaces JSF-2.1 Core Impl 2.1.1
> JBoss AS 6.0.0.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @Linux
> Chrome 12.0.742.112 @ Linux i686
>            Reporter: Ján Jamrich
>             Fix For: 4.1.0.Milestone2
>
>
> Client side validation is not performed reliable on calendar. There is example in Metamer (faces/components/richCalendar/csv.xhtml) with 3 different calendars, everyone validated to different date rule (past, future and last year), and without submit button.
> All calendars have set <a4j:ajax event="change" render="outputX" />, so there is expected validation to be fired immediately after value changes (picked from calendar). 
> When select wrong value in first calendar, validation message appears near this input. But if then try to select another value in second calendar, there wrong value in first calendar remains, as well as the validation message, but in second calendar no validation message appear, and selected value is set to calendar's input. The same behavior for last input.
> So this is quite confusing when select 3 wrong values, but only for first input is validation message displayed. (For JSR303/bean validation is displayed only one validation message for immediate validation - performed on blur event, but always for just left input - so user know that anything was done wrong with this input, not like in case of client side validation)
> Another problems appears with value change. Only for one input is value from calendar propagated to output element. Event the value entered (or picked from calendar popup) is correct. So, I can select correct value from first input (validated to past), and this value appears in output element. Then I select another correct value in second calendar input validated to future, but this value doesn't appears in output.
> This is different behavior than for other validation types (such as in bean/JSR303 validation), where is value propagated correctly - if correct of course.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira