Describe the bug
The arrow navigation is not longer working once there are null values provided for both min-date and max-date (and prevent-min-max-navigation is enabled)
If one or both of them are not null everything works as expected.
When both are null (which is according to the docs the default value for those props) the navigation does not react to user input at all.
The buttons are not visually disabled. They appear clickable but nothing happens
when min and max are null I think the intended behaviour is that there are no limitations (month and year change work, too)
this can be workarounded like :prevent-min-max-navigation="!!(minDate || maxDate)" but should not be required IMO.
Describe the bug The arrow navigation is not longer working once there are null values provided for both min-date and max-date (and prevent-min-max-navigation is enabled)
If one or both of them are not null everything works as expected. When both are null (which is according to the docs the default value for those props) the navigation does not react to user input at all.
To Reproduce https://codesandbox.io/p/sandbox/vue3-datepicker-min-max-issue-fms5nn
Expected behavior prevent-min-max-navigation should behave the same in this case like its: ":prevent-min-max-navigation="false"
Desktop & mobile (please complete the following information):