If someone can help me… I am running into two related limitations with the Date/TimePicker plugin on native mobile, and wondering if others have found cleaner solutions than what I’ve got.
1. No single field for both date and time
I was hoping to let users pick a date and time in one input, but the plugin’s “Date & Time” input type only lets the user pick a date and doesn’t expose a time-selection UI at all, even though the underlying value always includes a time component (defaulting to the current time, no custom time). To actually let users choose a custom time, I’ve had to add a second, separate picker element set to “Time” input type, and combine both values afterward using :change time to when saving. Is there a way to get one single element to let users pick both date and time interactively, or is two separate elements the expected approach?
2. Can’t let users tap directly into a saved time to edit it
My time field is stored as text (needed to work around a data type issue combining date+time, happy to explain further if needed). Because of that, the Date/TimePicker element can’t take this saved text value as its Initial Content so it throws a type error, since it expects a date type value even in Time only mode.
To work around this, I built a “tap to reveal” pattern… a styled Text element displays the saved time, and tapping it swaps in the actual picker (via a page property + conditionals). This works, but the picker itself doesn’t open its interactive time-selection UI on that same tap, the user has to tap once to reveal the picker, then tap again to actually open it and choose a new time.
I’ve tried:
- “Set focus to an input element” targeting the picker, right after the reveal step with no effect
- Adding a short pause (300ms) before the focus step with no effect
- Checked for a plugin-specific “open/show” action, which doesn’t seem to exist
Is there a way to get this down to a single tap, or is a two-tap edit flow simply a limitation of this plugin on native mobile? Also open to hearing if a different plugin handles either of these two issues more natively.
Thanks!