bug: datetime, pressing up and down in text entry mode jumps to wrong item in wheel picker

[Ericlm]

Prerequisites

• [X] I have read the Contributing Guidelines.
• [X] I agree to follow the Code of Conduct.
• [X] I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

v7.x

Current Behavior

There seems to have issues with the ion-datetime component, when the time modal is focused and that we try to interact with it via arrow keys.

1. The hours does not seem to handle the current hour (that is, if it's 10 and then you press Up, it goes to 1)
2. When you continue pressing, it goes up to 19 and then goes back to 2.
3. Once it's back to 2, the minutes get incremented, but only 10 by 10

Note : In my timezone, the time is 0-23 based

Expected Behavior

1. Pressing an arrow should make it move 1 hour+-, starting from the current input hour
2. I guess the input should goes up to 23, then goes to the minutes (but it needs a focus state ?)
3. When the minutes wheel is focused, it should respect the step entered (and not be only 10 by 10 at the beginning)

Steps to Reproduce

I tried everything on the "basic usage" example of the ion-datetime component : https://ionicframework.com/docs/api/datetime#basic-usage

Code Reproduction URL

https://ionicframework.com/docs/api/datetime#basic-usage

Ionic Info

Not applicable (https://ionicframework.com/docs/api/datetime#basic-usage)

Additional Information

No response

[liamdebeasi]

Which browser are you testing this on?

[Ericlm]

I tested it on Firefox, Chrome and Safari (all on macOS)

[liamdebeasi]

Thanks for the additional information. I think the problem here is you've activated the "text entry mode" in the time picker. This allows users to type a time in instead of dragging/clicking. However, we set type="number" on the input, so using the arrow keys is incrementing or decrementing that time inside of the input which can cause strange behaviors. I'm not clear on whether arrow keys should work at the same time as keyboard entry, but I'll check with the team for clarification on that.

[Ericlm]

Alright, thank you for your help! :)