-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Calendar: Allow typing dates manually #4134
Comments
Should I work on it, are you guys planning to implement this feature ? @melloware |
you can give it a shot @userkks if you want! PR's are always welcome! |
Ok, @melloware, you can assign it me then. |
How's this going? Is @userkks proposal going to make it? Similar to time zone support, I see this as a fundamental feature of date pickers, as their point is to facilitate inputting dates, so the moment they get in the way of that, there is no point in using them. |
Describe the feature you would like to see added
As a user, I would like to be able to type dates using the keyboard, and not be forced to use the UI. A common case where this is necessary is having to type your birthday: using the UI would take lots and lots of clicks, while using the keyboard would be much more immediate.
Currently, the interaction with the calendar's input box is very cumbersome. Particularly, pressing delete/backspace will wipe out the entire input, making it impossible to make any type of correction, while unexpectedly trashing the user's current selection, forcing them to reselect a date from the beginning.
Another specific case where keyboard interaction is broken is selecting the current value and pressing a number. You can reproduce this directly in https://primereact.org/calendar by:
There are likely other cases...
In my opinion, the calendar is not usable as it is. In fact, we are currently deciding against it until these problems are solved, in favor of a plain input box, because we already foresee user complaints from putting it in place.
The text was updated successfully, but these errors were encountered: