DatePicker validation problem

[Jesper]

Hi,

Problem:

We want to use the non-strict mode to rather indicate that a manually entered value is wrong so that it should be changed.

But there seems to be a bug where the presented value in the field does not match the bound value and therefor does not indicate validation errors even tho it's outside the range of min max.

To replicate:

- Enter the field and select a date from the datepicker calendar, tab out of the field.

- Manually change the date in the textfield to an incorrect date outside of the range and tab out of the field (remember what date you choose).

- Enter the field and re-select a valid date from the calendar.

- Manually change the value in the textfield to the same incorrect value you tried the first time.

Now it shows a value outside of the range as a valid value and it does not match the bound-value wich still is the last valid value.

You can replicate this on the DatePicker Demo - Date Range

[Berly Christopher]

Hi Jesper, 

  

Greetings from Syncfusion support. 

  

We have confirmed the reported issue “While entering same invalid value twice, then entered value persists in the DatePicker component” as a bug at our end and this fix will be included in our weekly patch release scheduled on 2^nd December 2020. We appreciate your patience until then.  

  

You can track the status of the reported issue from the below feedback. 

Feedback Link: https://www.syncfusion.com/feedback/19814/  

  

Regards, 

Berly B.C