-
Notifications
You must be signed in to change notification settings - Fork 89
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
When month selector is open, change date by year instead of month #114
Comments
Thx for suggestion i've implemented your snippet code on my project locally. Very helpful! |
The calendar supports arrows and page up/down keys currently. In the next version the arrows will control the current context (day, year, month, or time picker) and the page up/down arrows will control the "next" level of picker (ex: on day picker they move months [like today], on month picker they control years, etc). I may be able to allow some customization of the keys but I think what I have coded in the new version currently is a more intuitive default implementation for keyboard users than what is requested here. |
Okay, a question I have then is, who is a keyboard user... Thank you for replying. |
The arrow UI elements are still present in the new version and work the same as page up/down keys when clicked. |
svelte-calendar@3.x was recently released and has an updated UX around the day, month, and year pickers along with many other enhancements and some breaking-changes to the component's API (hopefully all for the better). Feel free to check it out and provide feedback here or in a new issue. |
Looks great will start using now! |
Hi, when you open the month selector I would like the arrows to change from 'changing months' to 'changing years'.
I have implemented this locally in an awkward sort of way by checking if its open or not, I'm wondering if its possible to get this developed properly?
Locally I just added this:
to the incremementMonth function in svelte-calendar/src/Components/DatePicker.svelte
Thank you.
The text was updated successfully, but these errors were encountered: