Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date Pickers and Calendars with minimum or maximum values should exclude invalid selections #15146

Open
MagisterXero opened this issue Dec 5, 2024 · 0 comments

Comments

@MagisterXero
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant