v3.1.1

Bug fixes

• Fixed Clock re-opening on click, which may have caused unpredictable behavior.

v3.1.0

What's new?

• Brand input rendering algorithm was implemented. It should be more reliable, especially for zh-CN locale.

What's changed?

• Clock widget will no longer close automatically on any value change.

Bug fixes

• Fixed clock widget not closing when input was blurred using the keyboard.

v3.0.0

See Upgrade guide from version 2.x to 3.x.

What's new?

• Inputs now automatically select on focus.
• Leading zeros are now wrapped in a <span /> element with react-time-picker__inputGroup__leadingZero class name for easier styling.
• Internal changes in TimeInput component that will allow for more refined styling of React-Time-Picker along with React-DateTime-Picker and React-TimeRange-Picker.

Bug fixes

• Fixed input height that could be off by 2 pixels on some devices.

v2.8.0

What's new?

• You can now attach event props (onClick, onKeyDown...) directly to React-Time-Picker root.
• Updated documentation to make it clear how to remove clockIcon and clearIcon.

What's changed?

• Auto resizing input fields mechanism has been improved.

Bug fixes

• Removed needless update when the user clicked somewhere on the screen while the calendar in React-Time-Picker was closed.

v2.7.2

What's changed?

• Updated all dependencies.

Bug fixes

• Fixed TimeInput not working properly on older (<16.3) versions of React.
• Updated get-user-locale dependency which fixes uncaught error on IE11 caused by Array.prototype.includes not being implemented.

v2.7.1

Bug fixes

• Fixed clock icon shown when disableClock flag is set to true (#11).

v2.7.0

What's new?

• Added disableClock flag that, well, disables clock (#9, #10). Thanks, @twinraven!

Bug fixes

• Fix min/max values not properly applied to MinuteInput, SecondInput.
• Fix an issue with validating forms when minTime was more detailed than the user could choose (e.g. minTime="23:41:20" and maxDetail="hour").

v2.6.0

What's changed?

• React-Time-Picker now uses get-user-locale to get user's locale data. This should be more reliable, especially on macOS/iOS prior to 10.2.

v2.5.2

What's changed?

• Clearing inputs manually will call onChange with null value, just like clearing it with clear button does.

Bug fixes

• Fixed AM/PM dropdown not appearing on some locales (e.g. en-AU).
• Fixed native input (not visible for most users, stays hidden; it's there for accessibility purposes) treating time as UTC, instead of local user's time.
• Fixed native input allowing to change seconds if maxDetail was set to minute.

v2.5.1

Bug fixes

• Fix an error causing hour 0 to be displayed as 0 am instead of 12 am in 12-hour time format.