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

bug(DateTimeRange): Visible selected range is kept after closing the component by losing focus #5383

Open
1 task done
jvk-digres opened this issue Feb 17, 2025 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jvk-digres
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

DateTimeRange keeps visible selected range after closing it by clicking outside the component/losing focus and the Value property remains the same.

Expected Behavior

I would expect the component to set its range back to the Value property after I close it by clicking outside.

Interactive render mode

Interactive Server (Interactive server-side rendering (interactive SSR) using Blazor Server)

Steps To Reproduce

This doesn't need a reproducible build since it's visible in blazor.zone docs imo: https://www.blazor.zone/datetime-range.

  1. Open the DateTimeRange component
  2. Select some range
  3. Click "Ok"
  4. Open the component again
  5. Select different range
  6. Click outside the component to close it without clicking on "Ok"
  7. Open the component, visible range is set to the last selected value but the Value property is not

Exceptions (if any)

No response

.NET Version

NET8.0

Anything else?

No response

@jvk-digres jvk-digres added the bug Something isn't working label Feb 17, 2025
Copy link

bb-auto bot commented Feb 17, 2025

@jvk-digres Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

@bb-auto bb-auto bot added this to the v9.3.0 milestone Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants