Gutenberg publish panel does not respect lowercase a in g:i a time format.

[truptikanzariya]

Description

The Gutenberg publish/schedule panel does not fully respect the site's configured.

Expected Result:
The time selector should display lowercase am/pm because the selected PHP time format uses lowercase a.

Example:
12:32 pm

Actual Result:
The Gutenberg publish panel displays uppercase AM/PM instead.

Example:
12:32 PM

Additional Notes:
When using g:i A, uppercase AM/PM is correct.
When using H:i, the editor should use 24-hour format without AM/PM.

Step-by-step reproduction instructions

Steps to Reproduce:

1. Go to Dashboard → Settings → General
2. Set Time Format to: g:i a
3. Open the Block Editor (Gutenberg)
4. Check the Publish/Schedule panel time selector.

Screenshots, screen recording, code snippet

Dashboard.test-wordpress.WordPress.webm

Environment info

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[im3dabasia]

Thanks for the report and steps to reproduce. I checked this. Found that the published date and time on the frontend will still show exactly as set in your sites time format settings. So there's no impact on what visitors see.

The AM/PM toggle, in the editor is a display option that works on its own. It's a point that the editor should ideally match the sites format. This could be something to discuss further.

I would love to hear what others think about this.

[t-hamano]

Date and time formats are solely for configuring how they are displayed on the frontend, and I don't think those rules apply to the editor UI where dates and times are set.

If we want to apply formatting to the editor UI, we would need to add an option to toggle case in the DateTimePicker component, but I'm not sure if that's worthwhile.

Personally, I suggest closing this issue as "not a bug."

[Mamaduka]

+1 for "not a bug". Components can use different designs/aesthetics, and not every piece of the editor is, or should be, controlled by these settings.