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
Hi Team,
the Timepicker-Field does not change it's value when Cut, Backspace and Delete events take place.
If a value gets deleted the first time, the default value (instead of the shown input value) is published. If the value gets deleted a second time, there is no update of the value at all. The timepicker itself shows 'HH:MM' in the second case. I would expect that there would either be an update of the time to the default value or a null /undefined value.
The shown value should always be represented in the published value.
Hi Team,
the Timepicker-Field does not change it's value when Cut, Backspace and Delete events take place.
If a value gets deleted the first time, the default value (instead of the shown input value) is published. If the value gets deleted a second time, there is no update of the value at all. The timepicker itself shows 'HH:MM' in the second case. I would expect that there would either be an update of the time to the default value or a null /undefined value.
The shown value should always be represented in the published value.
I implemented the TimepickerField like this:
The text was updated successfully, but these errors were encountered: