Skip to content

Releases: wojtekmaj/react-time-picker

v2.3.2

04 Apr 11:01
Compare
Choose a tag to compare

Bug fixes

  • Fixed Clock widget opening for disabled time picker on Internet Explorer due to IE's non-standard behavior.

v2.4.0

31 Mar 18:52
a368934
Compare
Choose a tag to compare

What's new?

  • React-Time-Picker is now fully compatible with React 17 (sic!). Minimum version requirement remained unchanged (#5).

v2.3.1

14 Mar 22:28
Compare
Choose a tag to compare

Bug fixes

  • Fixed a configuration bug that could have caused React-Time-Picker to behave unexpectedly on React 15.x environments.

v2.3.0

07 Mar 22:51
Compare
Choose a tag to compare

What's new?

  • You can use disabled prop to disable the time picker.

Bug fixes

  • Fixed TypeError: Object doesn't support property or method 'isNaN'. error that might have appeared on Internet Explorer 11 in some cases.

v2.2.0

04 Feb 13:25
Compare
Choose a tag to compare

What's new?

  • Various performance and architecture optimizations.

Bug fixes

  • Fixed an edge case when rendering two time pickers in different locales would cause the second time picker to overwrite locale settings of the first one.

v2.1.3

06 Jan 11:08
Compare
Choose a tag to compare

What's new?

  • You can now set a custom name using name prop. Default name remains "time".

Bug fixes

  • Minor accessibility fix in Test suite.

v2.1.2

30 Dec 23:05
Compare
Choose a tag to compare

What's new?

  • Minutes and seconds smaller than 10 will now have leading zero rendered.

v2.1.0

27 Dec 08:47
Compare
Choose a tag to compare

What's new?

  • Compiled files are now placed in a standard ./dist category.
  • Improved input scaling when using non-standard font sizes.
  • Sample and Test suites are now using Parcel for bundling.
  • Updated development platform:
    • Updated Jest to version 22.

v2.0.0

17 Dec 20:24
Compare
Choose a tag to compare

React-Time-Picker is now on NPM and Yarn! 🎉

As React-Time-Picker name was previously used by another library, to avoid confusion, versioning had to be aligned with preexisting npm package.