Component: Calendar #13807
Labels
Status: Discussion
Issue or pull request needs to be discussed by Core Team
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Type: New Feature
Issue contains a new feature or new component request
Describe the feature you would like to see added
Allow users to type the date with any punctuation they want (dash, slash, period, no spaces or punctuation but 8 digits) and reformat it on blur (when leaving the field).
Also, allow users to enter 2 digits for the year.
Is your feature request related to a problem?
This is a standard approach with good design--any UX or usability person would tell you this. The basic UX rule I'm following with this approach is to allow the UI to be forgiving. Don't penalize the user for your bad UI. (I'm not sure you have a user experience designer on your team given all the common UX rules you don't follow -- or you don't listen to your UX people. Not sure which. Please get a good UX person on your team and address all the other similar issues with your UI.)
Allowing users to enter only digits is also much more efficient for high-powered users who are fast on the keyboard (this is my user base who work on company-wide internal applications all day long).
Finally, removing the "incorrect" entry on blur is a bad user experience. You've removed the user's work and you did it without telling them -- 2 UX sins in one interaction.
Describe the solution you'd like
Allow user to type the date with any punctuation they want (dash, slash, period, no spaces or punctuation but 8 digits) and reformat it on blur (leaving the field).
Also, allow for the option of coding the field to allow for the user to enter 2 digits for the year if accompanied by punctuation. Allow the developer to determine the year in specific instances.
For example, all these entries should be allowed, and reformatted on blur:
12-12-2023
12/12/2023
12.12.2023
12122023
12-12-23
All would be reformatted on blur as:
12/12/2023
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: