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
Is your feature request related to a problem? Please describe.
If a Date Picker or Calendar component is given a minimum or maximum value, it stands to reason that the ability to view selections outside of those confines should be removed.
Describe the solution you'd like
Given that a minimum value has been set, prevent the Calendar from navigating to dates prior to the minimum and hide them from being seen.
Given that a maximum value has been set, prevent the calendar from navigating to dates after the maximum and hide them from being seen.
Additional context
Allowing someone to see potential selection criteria cannot be selected due to hard limits is a design flaw. It misleads the user into thinking that they could potential select a date by allowing traversal of calendar object to values that cannot be selected. Therefore all values prior to a set minimum, or after a set maximum, should be hidden to prevent confusion of usage. By hiding these, we guide the user to the intended selection criteria more smoothly and allow them to have a better user experience in the process by removing potential pitfalls.
This doesn't apply to dates within the minimum and maximum that are designated as disabled dates, because those are separately calculated and thus would not be affected by the hiding of dates.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If a Date Picker or Calendar component is given a minimum or maximum value, it stands to reason that the ability to view selections outside of those confines should be removed.
Describe the solution you'd like
Given that a minimum value has been set, prevent the Calendar from navigating to dates prior to the minimum and hide them from being seen.
Given that a maximum value has been set, prevent the calendar from navigating to dates after the maximum and hide them from being seen.
Additional context
Allowing someone to see potential selection criteria cannot be selected due to hard limits is a design flaw. It misleads the user into thinking that they could potential select a date by allowing traversal of calendar object to values that cannot be selected. Therefore all values prior to a set minimum, or after a set maximum, should be hidden to prevent confusion of usage. By hiding these, we guide the user to the intended selection criteria more smoothly and allow them to have a better user experience in the process by removing potential pitfalls.
This doesn't apply to dates within the minimum and maximum that are designated as disabled dates, because those are separately calculated and thus would not be affected by the hiding of dates.
The text was updated successfully, but these errors were encountered: