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

Component: Calendar #13807

Closed
UXRocks opened this issue Oct 4, 2023 · 4 comments
Closed

Component: Calendar #13807

UXRocks opened this issue Oct 4, 2023 · 4 comments
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

Comments

@UXRocks
Copy link

UXRocks commented Oct 4, 2023

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

@UXRocks UXRocks added 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 labels Oct 4, 2023
@chrisH-07
Copy link

Hi, can you please assign me to this issue?

@JohnG878
Copy link

JohnG878 commented Nov 5, 2023

I have another request that I think it can be part of this issue. It would be great if I could not only input text to be parsed into a date, but if there were also buttons and shortcuts on the calendar that would allow me to navigate to today, yesterday, last week, next week, last month, next month... I often need to pick dates from the past or future and the current process which requires multiple clicks can be quite time-consuming. Having this feature would be immensely helpful.

image

@x-fes54
Copy link

x-fes54 commented Nov 6, 2023

Hi all, I agree this would be useful feature. I think this UI would be better:

image

Just add something like this for week and then create a similar approach for the month. This should be more handy. Buttons may not be necessary up to "+6". This is just a sketch.

chrisH-07 pushed a commit to chrisH-07/primeng that referenced this issue Nov 12, 2023
…ormat and shortcut buttons for easy navigation
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

5 participants