RadzenDatePicker: Changing months or years should not change the selected date till one is clicked. #224

Closed
opened 2026-01-29 17:33:44 +00:00 by claunia · 6 comments
Owner

Originally created by @szalapski on GitHub (Oct 13, 2021).

Describe the bug
Changing months should not change the selected date, as the same day-of-month in a different month is very unlikely to be the date they want, and it is far more likely that the user is paging around to view the calendar and find the date they want, or perhaps to cancel.

To Reproduce
On any date picker, go to the next month. Notice that merely changing the month changes the selected date to be in the new month. This is contrary to how all date pickers elsewhere work.

Expected behavior
Show the next month with nothing selected, retaining the current value of the date.

I hope you will prioritize this, as it makes the date picker unusable for me.

Originally created by @szalapski on GitHub (Oct 13, 2021). **Describe the bug** Changing months should not change the selected date, as the same day-of-month in a different month is very unlikely to be the date they want, and it is far more likely that the user is paging around to view the calendar and find the date they want, or perhaps to cancel. **To Reproduce** On any date picker, go to the next month. Notice that merely changing the month changes the selected date to be in the new month. This is contrary to how all date pickers elsewhere work. **Expected behavior** Show the next month with nothing selected, retaining the current value of the date. I hope you will prioritize this, as it makes the date picker unusable for me.
Author
Owner

@brcaswell commented on GitHub (Oct 13, 2021):

I agree that automatically selecting a date when using these buttons to navigate to the correct date is undesirable behavior. It's a bit of a UX consideration, but certainly this behavior drives unnecessary changes.

Perhaps we can define an optional behavior option/parameter to pass to the component to drive this sort of expectation and behavior of the control. We should use the current behavior as the default so it won't immediately impact the control usage.

@brcaswell commented on GitHub (Oct 13, 2021): I agree that automatically selecting a date when using these buttons to navigate to the correct date is undesirable behavior. It's a bit of a UX consideration, but certainly this behavior drives unnecessary changes. Perhaps we can define an optional behavior option/parameter to pass to the component to drive this sort of expectation and behavior of the control. We should use the current behavior as the default so it won't immediately impact the control usage.
Author
Owner

@szalapski commented on GitHub (Oct 13, 2021):

@enchev, thanks for the quick action! I'll try it out as soon as I can.

@brcaswell, I respectfully submit that the current behavior is so wrong that the current behavior should be fixed, not maintained--But I appreciate the concern too.

@szalapski commented on GitHub (Oct 13, 2021): @enchev, thanks for the quick action! I'll try it out as soon as I can. @brcaswell, I respectfully submit that the current behavior is so wrong that the current behavior should be fixed, not maintained--But I appreciate the concern too.
Author
Owner

@szalapski commented on GitHub (Oct 13, 2021):

@enchev, I don't see release plans on GitHub...I assume I can't use this yet?

@szalapski commented on GitHub (Oct 13, 2021): @enchev, I don't see release plans on GitHub...I assume I can't use this yet?
Author
Owner

@akorchev commented on GitHub (Oct 13, 2021):

@szalapski we make releases every other day. If you need it sooner you can add the source to your application. Check the RadzenBlazorExamples.csproj to see how we do it.

@akorchev commented on GitHub (Oct 13, 2021): @szalapski we make releases every other day. If you need it sooner you can add the source to your application. Check the RadzenBlazorExamples.csproj to see how we do it.
Author
Owner

@szalapski commented on GitHub (Oct 13, 2021):

Wow, great, thanks!

On Wed, Oct 13, 2021, 9:16 AM Atanas Korchev @.***>
wrote:

@szalapski https://github.com/szalapski we make releases every other
day. If you need it sooner you can add the source to your application.
Check the RadzenBlazorExamples.csproj to see how we do it.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/radzenhq/radzen-blazor/issues/249#issuecomment-942353181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUY5MIPXGVZYAB4MG7QEFLUGWIFDANCNFSM5F4DPAJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@szalapski commented on GitHub (Oct 13, 2021): Wow, great, thanks! On Wed, Oct 13, 2021, 9:16 AM Atanas Korchev ***@***.***> wrote: > @szalapski <https://github.com/szalapski> we make releases every other > day. If you need it sooner you can add the source to your application. > Check the RadzenBlazorExamples.csproj to see how we do it. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/radzenhq/radzen-blazor/issues/249#issuecomment-942353181>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAUY5MIPXGVZYAB4MG7QEFLUGWIFDANCNFSM5F4DPAJA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >
Author
Owner

@szalapski commented on GitHub (Oct 15, 2021):

I tried this today; thank you for the fix, @enchev .

It still isn't quite right; can you reopen for a minor tweak? The class rz-state-active still appears on one day no matter what month you have navigated to, so the date seems to be "selected" even though it really isn't. Can this be fixed so that only the actual selected date in its proper month and year appears with a colored background, rather than having one in every month?

Example: The current selected date is June 1, but July 1 appears improperly as if it were selected. August 1, etc, would also show selected.

image

@szalapski commented on GitHub (Oct 15, 2021): I tried this today; thank you for the fix, @enchev . It still isn't quite right; can you reopen for a minor tweak? The class `rz-state-active` still appears on one day no matter what month you have navigated to, so the date seems to be "selected" even though it really isn't. Can this be fixed so that only the actual selected date in its proper month and year appears with a colored background, rather than having one in every month? Example: The current selected date is June 1, but July 1 appears improperly as if it were selected. August 1, etc, would also show selected. ![image](https://user-images.githubusercontent.com/2723505/137419459-eefa39d8-d1d6-4ac1-9569-11ea1a5ce88e.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#224