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

Datepicker UX Improvement: Enable selection of year #5321

Closed
kasperhhk opened this issue Jun 23, 2017 · 5 comments
Closed

Datepicker UX Improvement: Enable selection of year #5321

kasperhhk opened this issue Jun 23, 2017 · 5 comments
Labels
area: material/datepicker feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@kasperhhk
Copy link

Bug, feature request, or proposal:

Want to be able to select year

What is the expected behavior?

Being able to select year without having to +/- 1 year at a time

What is the current behavior?

Currently you have to +/- increment/drecrement the year by 1 every click.
It would be better to be able to select the year somehow, not sure what the best solution is.

What are the steps to reproduce?

Open the datepicker and try to select 1985, then try to go back to 2017.
It takes a lot of clicks.

you can check you own example to try it out:
https://material.angular.io/components/datepicker/examples

What is the use-case or motivation for changing an existing behavior?

When you have more than a couple of years available for the user to select from it quickly becomes tedious and frustrating going from one end to the other.
If it's easier solved by reloading the page, then it's flawed.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

material 2 beta 7

Is there anything else we should know?

@donroyco
Copy link
Contributor

Your title is misleading. Your suggestion is a UX improvement to the current solution.

@kasperhhk kasperhhk changed the title Datepicker unable to select year Datepicker UX Improvement: Enable selection of year Jun 23, 2017
@julianobrasil
Copy link
Contributor

julianobrasil commented Jun 26, 2017

It'll be eventually added. See comment #675 (comment) and the following discussion. In fact you're asking for something not planned, I think. It's worth copying this sugestion in #675, where they're tracking other sugestions to the datepicker.

@kasperhhk
Copy link
Author

I'd like to note that on a mobile device, if you want to change years it is very easy to accidentally trigger the zoom functionality of the device because you have to tap once per year increment / decrement.

@jelbourn jelbourn added discussion feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Jul 7, 2017
@mmalerba mmalerba added needs: discussion Further discussion with the team is needed before proceeding and removed discussion labels Mar 3, 2020
@annieyw
Copy link
Contributor

annieyw commented Mar 29, 2021

Closing this because the datepicker now has a year selection view.
Screen Shot 2021-03-29 at 2 17 41 PM

@annieyw annieyw closed this as completed Mar 29, 2021
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: material/datepicker feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

7 participants