useTwentyfourHour hour-range is 01 - 24, should be 00 - 23

[drsnok]

• Operating: Windows 10
• Browser: Chrome 103.0.5060.66, Edge 103.0.1264.44
• Version of the plugin. 6.0.0-beta9.
• Stackblitz fork: https://stackblitz.com/edit/tempus-dominus-v6-next-ajtgmm?file=index.js
• Browser's locale: sv-SE

When using the useTwentyfourHour-setting the hour-range is between 01 - 24, should be 00 - 23.
Maybe related to this ticket?

[drsnok]

Specifying a locale seems to fix it:

localization: { locale: 'en-GB' },

[Eonasdan]

This is fixed in beta9

[confuzeus]

The issue is still here in beta9.

Without specifying a locale, clock is 1-24.

[chrischu]

This bug definitely still exists in 6.2.4, even when specifying a locale.

This can even be reproduced on https://getdatepicker.com/6/plugins/customDateFormat.html by

• setting the locale to "default"
• clicking change
• the display now uses 1-24 instead of 0-23

Afterwards changing the locale back does NOT fix the issue, so I'm thinking there bug happens only when changing the locale for the first time or something.

[confuzeus]

I switched to flatpicker because I couldn't figure out to solve this issue.

[chrischu]

The problem is actually Chrome!

Running Intl.DateTimeFormat('en-US', { hour: 'numeric', hour12: false }).formatToParts(new Date(2000, 1, 1, 0, 0, 0))[0].value returns 00 in Firefox and 24 in Chrome!

[chrischu]

But is apparently also locale-dependend (when using en-GB instead of en-US it returns 00).

[chrischu]

I found somewhere that setting hourCycle: 'h23' should help, but at least in my case it doesn't :(.

[chrischu]

Found some new information: apparently hour12: false overrides hourCycle: 'h23', so what does work in both Firefox/Chrome is Intl.DateTimeFormat('en', { hour: '2-digit', hourCycle: 'h23' }).formatToParts(new Date(2000, 1, 1, 0, 0, 0))[0].value.