Selecting an AM will redirect the datepicker view to a PM for 24h timeMode.

I am using create-react-app as my development template. It has json-loader and i’ve imported everything as per the guide. onTimeChange, it calls a function to set the time to the state, which then feeds back into the TimePicker to via the time prop to update the view.

    handleTimeChange(time) {
        console.log(time)
        this.setState({ time });
    }

    render() {
        const { time } = this.state;

        return (
            <div className="form-group">
                <TimePicker
                    theme="classic"
                    time={time}
                    timeMode="24"
                    onTimeChange={this.handleTimeChange.bind(this)} />
            </div>
        );
    }

The problem comes in when I select the time, such as 1:00. I’ve logged what i get back from the onTimeChange method to compare the results between the view and the console.

and here is me selecting 13:00

both examples change the date picker time to 13:00, i’m just confused as to why it does it on the first one?

[ecmadao]

Sorry to reply you late. I had some personal trivia to deal some days ago, and now I’m coming back to fix this issue. First thank you so much for your enthusiasm to help me find these bugs. It’s my fault that now find these problems, and now I make some changes for this module:

1. If you send time props for react-times component, then when initialize, it won’t use time zone to render current time.
2. When user chose a time, component will not use time zone either (Cause users know what time they have chosen, so there is need to guess their time zone and recheck the time).
3. So now, only by sending a timezone props can make component use time zone when render time.

Now I have made a new version 2.2.8 to publish these changes. Would you like to update your dependency and check again? Thanks!

[ecmadao]

So strange. It worked well for me so I can’t reappearance this bug. But by looking your gif, it really looks like the bug which happened before v2.2.7. Can you reinstall this package, or clean browser cache? Cause it’s only a little change from v2.2.6 to v2.2.7, and maybe node module system or browser cached the required file. It’s only a guess, and I’m still debugging to check if any other bug exist.