I am using a RadDatePicker with a standard ASP.NET Required Field Validator control. Our users have reported what they believe is a bug in the way that these two controls work together to valdate and prevent post back of a page.
To setup the situation, you need a RadDatePicker with the MaxDate and MinDate configured. So, lets say the MaxDate is 30/06/2010 and the MinDate is 01/06/2010.
The scenario:
1. Type an out of range date into the textbox part of the date picker - Required Field Validator is displayed, post back prevented.
2. Type a valid date into the textbox part of the date picker - Required Field Validator is not displayed, post back allowed.
3. Re-type the out of range date into the textbox part of the date picker - Required Feild Validator is not displayed, post back allowed.
We would expect the post back to be prevented because the date is out of range. We would expect the value of whatever the Required Field validator is validating to be cleared if the value entered is invalid. Unfortunatly, we can only use a required field validator in this particualar scenario because of design constraints.
To setup the situation, you need a RadDatePicker with the MaxDate and MinDate configured. So, lets say the MaxDate is 30/06/2010 and the MinDate is 01/06/2010.
The scenario:
1. Type an out of range date into the textbox part of the date picker - Required Field Validator is displayed, post back prevented.
2. Type a valid date into the textbox part of the date picker - Required Field Validator is not displayed, post back allowed.
3. Re-type the out of range date into the textbox part of the date picker - Required Feild Validator is not displayed, post back allowed.
We would expect the post back to be prevented because the date is out of range. We would expect the value of whatever the Required Field validator is validating to be cleared if the value entered is invalid. Unfortunatly, we can only use a required field validator in this particualar scenario because of design constraints.