You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the datepicker always defaults to displaying the current month with today's date highlighted when no value has been selected. While this behavior works for many use cases, it would be beneficial to have a property that allows developers to control the initial month displayed when the picker is opened and no date value is pre-filled.
For example:
If today's date is December 19, clicking the picker shows December by default.
A new property (e.g., defaultMonth) could enable the picker to open on a different month, such as January or any other specified month, improving flexibility for applications where the current month isn't the most relevant.
This feature would enhance usability for scenarios where users are more likely to select dates outside the current month, streamlining their interaction with the component.
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered:
Currently, the datepicker always defaults to displaying the current month with today's date highlighted when no value has been selected. While this behavior works for many use cases, it would be beneficial to have a property that allows developers to control the initial month displayed when the picker is opened and no date value is pre-filled.
For example:
If today's date is December 19, clicking the picker shows December by default.
A new property (e.g., defaultMonth) could enable the picker to open on a different month, such as January or any other specified month, improving flexibility for applications where the current month isn't the most relevant.
This feature would enhance usability for scenarios where users are more likely to select dates outside the current month, streamlining their interaction with the component.
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered: