Date time format fix#7195
Closed
estrattonbailey wants to merge 2 commits into
Closed
Conversation
Contributor
|
Contributor
|
did this in #7196 |
Contributor
|
FYI several users in this thread reported times being shown incorrectly, apparently on posts too: https://bsky.app/profile/pfrazee.com/post/3ldoxeka2uk2y e.g.: |
Closed
Contributor
|
I faced a timezone issue while exploring #6742. This was my solution at the time (I hope this helps). Since no longer relied on datetimeformat to output time, I thought it was no longer an issue and removed it. I sincerely apologize for the consequences of not testing it thoroughly. |
Contributor
Contributor
|
According to the first commit, the missing import has been added. Please see #7204. |
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
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.

DMs were showing as being sent at UTC instead of the user's local time zone on iOS and Android. This seems to have been introduced in #6742.
This new polyfill should allow us to specify a default timezone on app load, but this does not appear to work on iOS or Android. See first commit for that attempt.
In the second commit, I applied the "fix", which is to use the built-in
Intl.DateTimeFormatinstead of the polyfill. I have not yet confirmed if this regresses #6742.