And potentially seconds (if that feature is added).

I find that when working with times in the day, it's easy to reason about it when just using minutes as the value- as in the total minutes past 00:00 in the day. Its a nice single value to pass around and can easily be converted to hours and minutes again for display.

I will be using the separated out hours and minutes for now, but just t

Describe the bug
Prop fadeToColor doesn't accepts rgba color.

Expected behavior
Ideally it should accept any valid color, such as rgba.

To Reproduce

export default class App extends Component {

  state = { date: new Date() }

  render = () =>
    <DatePicker
      date={this.state.date}
      onDateChange={date => this.setState({ date })}
      fade

<TimePicker
 id={section}
 trigger={this.getTrigger(section)}
 {...this.props}
 focused={focused}
 meridiem={meridiem}
 timeMode='12'
 onFocusChange={this.onFocusChange(section)}
 onTimeChange={this.onTimeChange(section)}
 time={hour && minute ? '6:20' : '5:45'}
/>

During the initial render the pointers are on the correct position like so

<img width="279" alt="Screen Sho

If you add a non number character, say the letter x, into the hour input on a 24 hour TimePicker, the minutes will be cleared out to the placeholder. If you do the same with a 12 hour TimePicker, the minutes are not cleared out. It's a little strange that the behavior is inconsistent.

Firefox:
<img width="466" alt="Screen Shot 2019-06-27 at 4 02 17 PM" src="https://user-images.githubuserconte

In trying to figure out why the example usage codes weren't giving me the same results in my app as in the docs, I decided to look at the dummy app to see how they were actually implemented there. I realized that I needed to give the component a value. Silly me; I should've figured that out sooner. But would be nice to note this in the docs and usage examples.