Setting timezone="UTC" for TimePickerElement should display "UTC" as the "hint" text, not "Monrovia, Reykjavik"

[macintacos]

I am trying to build a form for users to fill out, and it includes a time picker. I want to "force" users to use UTC for this time picker. However, when I set timezone="UTC", the label that is provided is "Monrovia, Reykjavik". This is causing a bunch of downstream confusion that I basically have no control over the representation of.

I could imagine two solutions to this:

• If I supply "UTC" as the timezone, it should just show "Time zone: UTC" as the "hint" under the form field.
• The TimePickerElement should allow users to specify its own hint, so that I can display whatever I want, as the builder of the form.

Category (place an x in each of the [ ])

• slack_sdk.web.WebClient (sync/async) (Web API client)
• slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
• slack_sdk.models (UI component builders)
• slack_sdk.oauth (OAuth Flow Utilities)
• slack_sdk.socket_mode (Socket Mode client)
• slack_sdk.audit_logs (Audit Logs API client)
• slack_sdk.scim (SCIM API client)
• slack_sdk.rtm (RTM client)
• slack_sdk.signature (Request Signature Verifier)

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[zimeg]

Hey @macintacos 👋 This is super interesting and seems unexpected... I'm finding similar results in Block Kit Builder which makes me think this is a server side issue instead of something that's specific to this SDK.

I'll raise this with the right teams and keep this issue open to track progress, but I'm not sure of a workaround that exists with the available fields of the timepicker element 😔 I know that might not be ideal for right now, although I'm hoping a fix can be found soon!

[macintacos]

Sounds good. If it gets resolved with a server-side update, that's good enough for me.

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[macintacos]

@zimeg any word from backend folks? Hesitant to close this until it's actually resolved.

[zimeg]

@macintacos I agree it's not a closed issue- no worries keeping it open! I just followed up with the team and it's a noted bug without an immediate fix ready.

If this continues to be confusing to your app users I'd also recommend emailing [email protected] since we can't provide a workaround at the SDK level at this time. Thanks for checking in! 🙏