We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Component
The hour-selector in an input with type="datetime-local" and step="1" does not allow to write a 2 digit number with the keyboard.
Here is a Gist that does not work. https://lit.dev/playground/#gist=3eedd3e52aa191e027d059e26869ff5e
I does work for some users, but not all. I have customers complaining about the behavior.
The workaround is to use the keyboard up/down to change the digit to its right value
No or unsure. This never worked, or I haven't tried before.
Current
Browser: Chrome and Edge OS: Windows
The text was updated successfully, but these errors were encountered:
What timezone and locale are you in that is giving the unexpected behavior?
Entering in "October 10, 2025 @ 10:10:10am" works for me, but I'm in GMT-7 on en-US, so my inputs take a different format.
I don't see an am/pm section in your input, so I think it may be a different 24-hour locale that behaves differently.
Sorry, something went wrong.
I am in Sweden with sv-SE as my locale., Timezone right now is GMT+2 here.
No branches or pull requests
What is affected?
Component
Description
The hour-selector in an input with type="datetime-local" and step="1" does not allow to write a 2 digit number with the keyboard.
Reproduction
Here is a Gist that does not work.
https://lit.dev/playground/#gist=3eedd3e52aa191e027d059e26869ff5e
I does work for some users, but not all. I have customers complaining about the behavior.
Workaround
The workaround is to use the keyboard up/down to change the digit to its right value
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
Current
Browser/OS/Node environment
Browser: Chrome and Edge
OS: Windows
The text was updated successfully, but these errors were encountered: