-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Hour input doesn't handle fast typing well, and converts input to unintended value #131
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 14 days. |
Yep that's a bug. We change focus on key up, and you can press next key (in this case: "4") down before the previous one (in this case: "3") is up. This results in "34" typed in a number input, which for gets "converted" to 24-hour time format, removing 24 hours, resulting in "10" in hour field. |
Type "345" into the hours input quickly, as if one were typing 3:45. Instead of '3' going into the hours input field, and '45' going into the minutes input field, the result is "10:05".
The text was updated successfully, but these errors were encountered: