With StrictMode="true" component doesn't always revert invalid text

[Chuck Richardson]

Hello,

When using the DatePicker as follows:

<Syncfusion.Blazor.Calendars.SfDatePicker @bind-Value="@CreationDateFilter" StrictMode="true"/>

@code{

public DateTime? CreationDateFilter { get; set; }

}

It starts out with a blank date as expected. If I enter a valid date or choose a valid date from the calendar that is populated as expected. If I overtype the valid date with an invalid string and tab out the previously selected date is set back into the text box as expected.

However, if I start out with a blank date and type an invalid string and tab out, the invalid string is retained rather than the text box reverting to blank which is what I would expect it to do.

Could you please advise how I can achieve this?

Thanks,

Chuck

[Ponmani Murugaiyan]

Hi Chuck, 

We able to replicate the reported issue in our end, we will update further details in 2 business days February 8, 2022. 

Regards, 

Ponmani M 

[Ponmani Murugaiyan]

Hi Chuck, 

We have considered the reported issue “DatePicker with strict mode true does not reset invalid date when previous value is null” as bug in our end. The fix will be included in the upcoming patch release which is expected to be rolled out on February 16, 2022. You can track the status using the below feedback link. 

https://www.syncfusion.com/feedback/32473/datepicker-with-strict-mode-true-does-not-reset-invalid-date-when-previous-value 

Regards, 

Ponmani M 

[Ponmani Murugaiyan]

Hi Chuck, 

We are glad to announce that fix for the issue “DatePicker with strict mode true does not reset invalid date when previous value is null" has been rolled out in our weekly patch release. We request you to upgrade the package to “19.4.52” version to get rid of this issue. Please find the sample below. 

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/DatePicker_Strictmode-437068932 

Regards, 

Ponmani M 

[Chuck Richardson]

Hi Ponmani,

I'm pleased to confirm that this issue has been resolved in 19.4.52.

Thanks for your help,

Chuck

[Ponmani Murugaiyan]

Hi Chuck, 

Welcome, we are glad to hear that the issue has been resolved.  

Regards, 

Ponmani M