Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Nullable value not working in FluentTimePicker #2230

Closed
hksalessio opened this issue Jun 20, 2024 · 0 comments
Closed

fix: Nullable value not working in FluentTimePicker #2230

hksalessio opened this issue Jun 20, 2024 · 0 comments
Assignees
Labels
status:needs-investigation Needs additional investigation
Milestone

Comments

@hksalessio
Copy link
Contributor

🐛 Bug Report

FluentTimePicker supports nullable values but when inserting and removing a value, the value stays at the last value (which is 00:00 because backspace sets it first back to 00:00 and then to --:--).
This is observable in the example on the demo page: https://www.fluentui-blazor.net/DateTime#defaulttimepicker

💻 Repro or Code Sample

2024-06-20-11-39-57.mp4

🤔 Expected Behavior

When using backspace to clear the value, it should still change to 00:00 first and when using backspace again it should change to null.

😯 Current Behavior

Using backspace twice leaves the value at 00:00.

@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label Jun 20, 2024
@vnbaaij vnbaaij added status:needs-investigation Needs additional investigation and removed triage New issue. Needs to be looked at labels Jun 20, 2024
@vnbaaij vnbaaij added this to the v4.8.1 milestone Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-investigation Needs additional investigation
Projects
None yet
Development

No branches or pull requests

3 participants