UX problem with bp:DatePicker in specific state

[liviriniu]

Hi there,

If before I show my bp:DatePicker for the first time to the user, I set its MinDate property to 1,2 or more months in the future, when it is first accessed it displays an unavailable current month. At the time of writing this, it is 13th of March so what the user sees when the popup is opened and then tries to see the calendar:

Then it jumps to the first available day when trying to navigate the control.

PS:
I did not find any markup property of the control that could set the visible start month.
The CalendarExtender from the ancestral AjaxControlToolkit had the StartDate property that addressed exactly this case.

[liviriniu]

This is kinda, sorta... bad.

I've created a new fresh DotVVM .NET Core project to make sure and isolate the buggy control.

Today's date is: 2025-02-14.

Case A. (successful)
If I configure the DatePicker like this and MaxRequestDate becomes December 2025:

All is well.

Case B. (fail)
If I dare to jump with MaxRequestDate to the next year (2026):

Click the month-year text and this appears:

No selection can be made and you cannot go back to selecting by day.
The field is rendered useless and the page must be refreshed. 👎

In a complex business UI scenario, the user is forced to close the form and lose any typed in data because the control in not usable anymore. 👎

[liviriniu]

also see this (again, about this control): https://forum.dotvvm.com/t/bp-datepicker-mindate-maxdate-limit-that-crashes-entire-pages/293