Skip to content
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

Closed
zachandblue opened this issue Dec 9, 2021 · 3 comments
Labels
bug Something isn't working fresh

Comments

@zachandblue
Copy link

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".

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot added the stale label Mar 14, 2022
@wojtekmaj wojtekmaj added bug Something isn't working and removed stale labels Mar 18, 2022
@wojtekmaj
Copy link
Owner

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.

@DSp4wN

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fresh
Projects
None yet
Development

No branches or pull requests

3 participants