Datetimepicker bug?

[pedrosino]

While editing a competition yesterday, I found that selecting October 15th 2016 is very messy. See gif below.
Basically the field is saved as 2016-10-16 on the database, but for some reason it appear as 2016-10-15 on the input. Also, when the datetimepicker opens, there are two (?!) day 15, one being to the right of everything else.

I'm able to click on the 16th and save, but on reloading the problem repeats.

Could this be something local? Can anybody try to replicate this?

[larspetrus]

It's probably some broken assumptions about time zones in the code.

Can you try it at different times of day and see if it acts differently?

[pedrosino]

Just tried again and got the same result.
I remember seeing this a couple weeks ago too, in another project of mine.

[pedrosino]

I was fixing a birthdate today and realised it also fails for october 1991:

[pedrosino]

For the record, I just created zpaulovics/datetimepicker-rails#83

[pedrosino]

zpaulovics/datetimepicker-rails#83 (comment)
Seems like there is hope :D

[ronaldmansveld]

@pedrosino

Are we still using that same library for the datepicker? Does the issue still exist? I see their last commit was in 2015, so that doesn't give much hope ;)

If we have moved to a different datepicker, then please close this ticket.

[pedrosino]

Yeah, it does:

[ronaldmansveld]

In that case we should move to a different datepicker, one that is still under active maintenance ;)

[UnsolvedCypher]

@pedrosino Could you check whether this branch still has the same issue?

[pedrosino]

@UnsolvedCypher Sorry for the delaty
It works fine with your branch, but also seems to work on the WCA website now:

[UnsolvedCypher]

Oh that's good to hear! In that case I guess this issue can be closed

[viroulep]

Love these kind of issues :)