Bug
Let's say the current time is 16:01.
If you set minimumDate to today at 16:31, and minuteInterval to 15, the lowest selectable time will be 16:30, even though this is below minimumDate.
This might be the behaviour of the native UIDatePicker, but wondering if it would still make sense to patch this in Javascript-land.
Environment info
Running 2.2.2
Bug
Let's say the current time is
16:01.If you set minimumDate to
today at 16:31, andminuteIntervalto15, the lowest selectable time will be16:30, even though this is belowminimumDate.This might be the behaviour of the native UIDatePicker, but wondering if it would still make sense to patch this in Javascript-land.
Environment info
Running 2.2.2