time-picker time-picker does not accept 24:00 as a valid value, and does thus not conform to ISO8601 5.3.2

time-picker does not accept 24:00 as a valid value, and does thus not conform to ISO8601 5.3.2

Open petersmoeller opened this issue 7 years ago • 6 comments

This is somewhat mentioned in issue 43: Issue 43

In Europe (and other military time / 24 hour clock using areas) 24:00 is a valid value so as to distinguish between the start of the day and the end of the day.

I'm aware that 24:00 wouldn't work when saved in a db. (ex. Python datetime.time() accepts only up to 23:59), but from a UX POV. it makes sense for the user to be able to choose 24:00.

As an example, lets take a Shift at a bar a friday night(Our current usecase). Some shifts start friday at 24:00 and ends saturday morning at 04:00. (Technically the shift is saturday from 00:00 to 04:00 but thats not how the user thinks about it).

What would be nice is some way to make 24:00 a submittable value(and then do the right things in backend). Would that be possible perhabs?

Context: http://forum.jquery.com/topic/timepickers-should-conform-to-iso8601-5-3-2-on-midnight-representations-accepting-24-00-as-a-valid-value

Feb 21 '18 08:02 petersmoeller

any update?

moment support k/kk format tokens from version 2.13.0: https://github.com/moment/moment/pull/3102, if time-picker change all format string from h/HH to k/kk, 24:xx will be supported?