This question is locked. New answers and comments are not allowed.
Hi,
we're having a problem with the max/min properties of the datepicker control and client side validation. In an older version, the client validation would mark input outside the max/min range as invalid, which is our desired behavior.
In this new version, it does however just change the date to the nearest valid date without indicating that anything is wrong (on blur). We use this in a medical system and changing a date in this manner may cause the user not to notice that the date was changed, which may lead to some potentially hazardous situations.
Is there any way to keep using client side validation to just make the user aware of a bad input instead, without changing the control's value? We could resort to custom js or server side validation, but it wouldn't be as good looking from a code point of view.
Thanks,
Igor
we're having a problem with the max/min properties of the datepicker control and client side validation. In an older version, the client validation would mark input outside the max/min range as invalid, which is our desired behavior.
In this new version, it does however just change the date to the nearest valid date without indicating that anything is wrong (on blur). We use this in a medical system and changing a date in this manner may cause the user not to notice that the date was changed, which may lead to some potentially hazardous situations.
Is there any way to keep using client side validation to just make the user aware of a bad input instead, without changing the control's value? We could resort to custom js or server side validation, but it wouldn't be as good looking from a code point of view.
Thanks,
Igor