FIX: Use profile timezone consistently for local dates display #36705
+35
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, local dates in posts used the browser's timezone (via moment.tz.guess()) while the bookmark "Date in post" option used the user's profile timezone. This caused a mismatch when a user's browser timezone differed from their profile setting. For example, a user with their profile set to "Asia/Singapore" but browser in UTC would see an event displayed as "7:19 AM" in the post, but the bookmark dialog would show "2:19 PM" for the same event. Now all local date displays consistently use the user's profile timezone when available, falling back to moment.tz.guess() only for anonymous users or when no profile timezone is set. Internal ref - t/170851
github-actions
bot
added
chat
janzenisaac
approved these changes
Dec 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, local dates in posts used the browser's timezone (via
moment.tz.guess()) while the bookmark "Date in post" option used the
user's profile timezone. This caused a mismatch when a user's browser
timezone differed from their profile setting.
For example, a user with their profile set to "Asia/Singapore" but
browser in UTC would see an event displayed as "7:19 AM" in the post,
but the bookmark dialog would show "2:19 PM" for the same event.
Now all local date displays consistently use the user's profile
timezone when available, falling back to moment.tz.guess() only for
anonymous users or when no profile timezone is set.
Internal ref - t/170851
BEFORE
BEFORE.mov
AFTER
AFTER.mov