You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have a duration field, I thought about common "timepicker" components to hack the UI... but it does not allow more than 24 hours as value... And I'm not a fan of 3 different inputs.
But I'm wondering if someone has a better approach? In term of UX it's a bit complex for a lambda user to understand the logic when typing multiple numbers it's sliding the category from minutes to hours.
Thank you,
Note: when I'm mentioning ISO 8601 in my case I'm just interested in what is after the T separation in the standard (to focus only on hours/minutes/seconds). Using it helps me then to make any additional verification or computation with known librairies.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I would like to have a duration field, I thought about common "timepicker" components to hack the UI... but it does not allow more than 24 hours as value... And I'm not a fan of 3 different inputs.
So I think masking may be the best approach.
For now I thought about a mask like:
But I'm wondering if someone has a better approach? In term of UX it's a bit complex for a lambda user to understand the logic when typing multiple numbers it's sliding the category from minutes to hours.
Thank you,
Note: when I'm mentioning
ISO 8601
in my case I'm just interested in what is after theT
separation in the standard (to focus only on hours/minutes/seconds). Using it helps me then to make any additional verification or computation with known librairies.Beta Was this translation helpful? Give feedback.
All reactions