[Timepicker] With null value, after selecting hour default time is current minute of now rather than a more logical default like 00

[dborstelmann]

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

1. Pass null to timepicker.
2. Select hour (defaults to nothing)
3. Select minute, defaults to whatever minute right now is, which is a strange default, especially considering hour is null to start.

Expected Behavior 🤔

1. Pass null to timepicker.
2. Select hour (defaults to nothing)
3. Select time, defaults to nothing or 00 (0 may be required because I understand changing hour sets a value, I think this new value should not have current time).

Context

When someone adds a new time to an object that doesn't have it, they are unlikely to have minutes defaulting to now. They are usually setting a value that is in the future and likely to be on an hour, or half hour, or maybe 15 minutes. But 0 is a more logical default than now.

[tomas-c]

Another issue with the current time being the default is that it does not respect minutesStep setting. If I set minutesStep=5 the initial value sometimes can default to, for example, 13.

[michal-perlakowski]

The same applies to seconds when using a Time Picker with seconds.