InputDate resets when typing 0 as day or month

[stefangross]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When using the default InputDate the whole component resets its values when entering the month or day starting with "0".

Here is a link to a video showing the issue:

Expected Behavior

When entering month or day and using keyboard input "0" to start the the entry i would expect the component not to reset and allow me to continue to type the value, for example "05" for the month of May

Steps To Reproduce

1. Use the default InputDate component bound to a date property
2. Go the the page where the component is used. Start entering a year (2023 for example) press tab to go to month and start with typing the number zero.
3. The component resets

Exceptions (if any)

none

.NET Version

6.0.400

Anything else?

PM> dotnet --info
.NET SDK (reflecting any global.json):
Version: 6.0.400
Commit: 7771abd614

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22000
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.400\

global.json file:
Not found

Host:
Version: 6.0.8
Architecture: x64
Commit: 55fb7ef977

.NET SDKs installed:
6.0.400 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.28 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Download .NET:
https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[TanayParikh]

Hey @stefangross, thanks for reporting. I just tried it out, and wasn't able to repro:

https://blazorrepl.telerik.com/cQkXEsPr45BOD5gO11

Can you please provide a minimal, public, github repo (or use the above repl to create the repo)?

Also, can you please confirm what culture you're using (this may be a localization related issue). For the record, I used en-US for the above repo.

Hi @stefangross. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[stefangross]

Hello @TanayParikh
If you switch to a nullable datetime in your model

    class Starship
    {
        public DateTime? ProductionDate {get;set;}
    }

then you get the behavior that I'm describing. I didn't realize they were connected.
But also, when you don't have a nullable datetime, then the validation gives an error as soon as you type "0" into month or day. Im guessing the two are related.
I've tried this with several different cultures, de-DE, sv-SE, fi-FI and en-GB

[MarvinKlein1508]

This also happens when binding to a html input of type date, time, month, datetime-local.

In my case it doesn't need to be nullable to get this behaviour.

As a workaround you can deny the set of the default value for your property. For example:

public DateTime Von
{
    get => _von; 
    set
    {
        if(value == new DateTime())
        {
            return;
        }

        _von = value;
    }
}

[MarvinKlein1508]

This issue might be connected with this one as well #40660