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.

Sign up for GitHub

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

Jump to bottom

The Next Year, Previous Year, Next Month, Previous Month, Month select and Year select are all not keyboard accessible. #35

Open

muztabadsi opened this issue Jun 5, 2018 · 1 comment

muztabadsi commented Jun 5, 2018

Next Year, Previous Year, Next Month etc has the tabindex="0" present, but when pressing Tab it closes the dapicker. Those control should get focus.

How can I fix this?

matoaaa commented Jan 27, 2020

From live demo [http://eureka2.github.io/ab-datepicker/]:

Tab / Shift+Tab If the datepicker is in modal mode, navigate between calander grid and close/previous/next selection buttons, otherwise move to the field following/preceding the date textbox associated with the datepicker

So this is by design.
But maybe it would be better to have the same behaviour as for modal also for datepicker in standard mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment