bug: time picker in ion-datetime does not let me select AM/PM using keyboard input #24070
Closed
4 tasks done
Labels
package: core
@ionic/core package
type: bug
a confirmed bug report
v6
issues specific to Framework v6
Milestone
Prerequisites
Ionic Framework Version
Current Behavior
In terms of accessibility on Web, I'm able to tab through to select a time using the time picker in
ion-datetime
by typing in values e.g.12
,tab
,35
, but using the keyboard I am not able to switch between AM/PM (typing in A or P doesn't work, and neither does up/down arrow keys)It also seems strange that I can use the scroll-wheel to select both times and AM/PM, but the up/down keys don't work for any of the input fields. This to me is a bug but if I need to put in a feature request instead, let me know and I will gladly do that!
In this screen recording, I'm using tab + keyboard to input into the component. When I reach the AM/PM section, I'm unable to switch from AM to PM using
A
,P
, or up/down arrow keys so I'm stuck.https://user-images.githubusercontent.com/7946204/137190396-f6c9036a-e3b9-48f1-ab54-95a60139124e.mov
Expected Behavior
Using a combination of number input and
tab
key, I should be able to type in any input into the numbers for the time picker, not just numbers, but alsoA
orP
to specify AM or PM when I get to the AM/PM selection.Using some combination of keyboard input, I should be able to safely input a time as well as the AM/PM value into the time picker of the
ion-datetime
component. I should be able to type the letterA
orP
to go to AM or PM.In addition, if I'm able to use the scroll wheel on a mouse to go scroll through the time or AM/PM selection, I should also be able to use up-down keyboard arrow keys for additional accessibility.
Steps to Reproduce
ionic serve
home.html
. I happened to be testing out the ion-datetime inside a modal, but this issue will happen regardless of being in a modal.Code Reproduction URL
https://github.com/bchehraz/ionic-v6-bugs
Ionic Info
Additional Information
Related feat request as well as the PR that implemented the feat, if that is helpful at all...
Feat request: #23768
PR: #23996
The text was updated successfully, but these errors were encountered: