Datepicker popup should close on blur event #1880
Comments
|
@julesbou After tabbing out of datepicker input, focus goes to the to the calendar itself (unless you have appended it to the This would be a nice feature, but I think it's more complex. |
|
I've added this fix to my project; I can't think of any use case where having the focus go to the calendar is something the user's would want If they're filling out the form strictly from the keyboard, they're going to want to get that date typed in and move to the next field, not tab through a bunch of controls in a calendar. |
|
@jayoungers Moving the focus to the calendar allows keyboard interaction, like arrow keys, page up/down etc. This is a standard pattern and many keyboard only users would want to use the calendar this way instead of writing the date, because navigating, they can for example see which dates are disabled etc. BTW datepicker's accessibility is a work in progress. |
|
@bekos "the standard pattern" that you identified in your previous post seems to be flawed. It's frustrating feature to everyone that has used it within our web app. Those that are filling in the form via keyboard always have to move their hands to a mouse to choose a date or click outside the datepicker. Many times the current date is the one they want. |
|
@bekos Just saw your response from earlier now: I can understand needing the ability for users to select dates via the keyboard, but I don't think the tab key is the way to do it. I'd recommend having the arrow keys control the calendar popup, and allow the tab key to move on to the next input as expected |
|
@Hamilton-Justin The latest released version of the datepicker does not follow this pattern! Feel free to experiment with #1922. |
|
Closing due to inactivity. Feel free to reopen if this is still an issue in UI Bootstrap 0.13.0 |
When tabbing out of a datepicker field, the datepicker remains open, it should be closed.
We're using this fix for now: StarterSquad/bootstrap-bower@902cc84
The text was updated successfully, but these errors were encountered: