10:27 p.m.
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)
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
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
New subject: [JBoss JIRA] Commented: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11246:
---------------------------------
Hi Jano, is this issue MyFaces specific?
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)
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
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] Commented: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich commented on RF-11246:
----------------------------------
Seems not, veri similar behavior found on calendar client validation on Mojarra 2.0.3, and
across the browsers (chrome, IE7, FF3.6)
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)
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
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 p.m.
New subject: [JBoss JIRA] Updated: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich updated RF-11246:
-----------------------------
Description:
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.
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.)
was:
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.
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)
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
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.
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
4:04 p.m.
New subject: [JBoss JIRA] Updated: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich updated RF-11246:
-----------------------------
Description:
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.)
was:
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.
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.)
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)
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
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
4:30 p.m.
New subject: [JBoss JIRA] Updated: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11246:
----------------------------
Fix Version/s: 4.1.0.Milestone2
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)
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
10:25 p.m.
New subject: [JBoss JIRA] Updated: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Component/s: component-input
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
7:06 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
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
2:35 a.m.
New subject: [JBoss JIRA] Updated: (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11246:
-----------------------------
Fix Version/s: 4.1.0.Tracking
(was: 4.1.0.Milestone2)
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.Tracking
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
8:24 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Fix Version/s: 4.2.0.Tracking
(was: 4.1.0.Tracking)
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.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem resolved RF-11246.
--------------------------------
Fix Version/s: (was: 4.2.0.Tracking)
Resolution: Rejected
required=true does not work with CSV
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
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Comment: was deleted
(was: required=true does not work with CSV)
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.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem reopened RF-11246:
--------------------------------
closed the wrong issue
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.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Fix Version/s: 4.2.0.Tracking
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.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Comment: was deleted
(was: closed the wrong issue)
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.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:42 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Jan Papousek updated RF-11246:
------------------------------
Affects Version/s: 4.2.0.CR1
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
Affects Versions: 4.2.0.CR1
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.3-Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Jan Papousek resolved RF-11246.
-------------------------------
Resolution: Duplicate Issue
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
Affects Versions: 4.2.0.CR1
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.3-Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 p.m.
New subject: [JBoss JIRA] (RF-11246) rich:calendar client side validation doesn't work reliable
[
https://issues.jboss.org/browse/RF-11246?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11246:
-------------------------------
Fix Version/s: (was: 5-Tracking)
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
Affects Versions: 4.2.0.CR1
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
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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4202
days inactive
4637
days old
richfaces-issues@lists.jboss.org
17 comments
8 participants
participants (8)
-
Brian Leathem (JIRA) -
Brian Leathem (Reopened) (JIRA)
-
Brian Leathem (Resolved) (JIRA)
-
Brian Leathem (Updated) (JIRA)
-
Jan Papousek (JIRA)
-
Jay Balunas (JIRA)
-
Ján Jamrich (JIRA)
-
Lukáš Fryč (JIRA)