This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Improve UI for input_datetime #3920
Comments
move[bot] commented on Dec 1, 2018, 3:14 AM UTC: raccettura commented on Jan 10, 2018, 4:44 PM UTC: Might be a wider discussion but can there be perhaps a flag to decide when to polyfill vs use native OS input methods? The reason I mention this is OS input methods don't work as well in all use cases, for example one that always annoys me is passcode for alarm in android pops up the full screen keyboard... hard to use with a wall mounted tablet. An option to reduce that to a polyfilled numeric input would be much more suited. For wall mount, I think in general the polymer based inputs are actually pretty nice with touch devices. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
move[bot] commented on Dec 1, 2018, 3:14 AM UTC:
baflo commented on Jan 4, 2018, 9:24 AM UTC:
The UI for input_datetime - at least for the time input - is very basic. Especially on mobile devices the experience is not very well. It doesn't even handle jumping from the "hours" field to the "minutes" field when two digits were entered.
Using HTML5 input elements like
<input type="time"/>
would allow the app to use the OS's time input methods, which should be much more elegant.Alternatively, I found this project: https://www.webcomponents.org/element/fooloomanzoo/datetime-picker
This issue was moved by iantrich from home-assistant/home-assistant-polymer#785.
This issue was moved by iantrich from home-assistant/ui-schema#209.
The text was updated successfully, but these errors were encountered: