Message timestamp in a channel shows yesterday for a message received 3 days ago #11460
Comments
chaitanyaprem
changed the title
|
@chaitanyaprem just a Q: have you by any chance been running the app (w/o quitting) non-stop for a few days? |
Yes, that is quite possible |
|
Yes, the same here, I'm running it for 2 days |
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
1 task
1 task
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates (StatusSharedUpdateTimer) - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates (StatusSharedUpdateTimer) - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates (StatusSharedUpdateTimer) - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates (StatusSharedUpdateTimer) - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
caybro
added a commit
that referenced
this issue
Feb 12, 2024
- introduce one global update timer, to be used in various components for date/time sensitive updates (StatusSharedUpdateTimer) - this timer runs only when the app is/becomes active - use the timer's `triggered()` signal to update the timestamp label when needed; ie. if it's to display a relative timestamp and it's currently visible Fixes #11460
alexandraB99
added
E:Desktop Bugfixes 2.28.0
and removed
feature
E:Desktop Features 2.28.0
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
In a channel, if the latest message is few days old the timestamp still indicates as "yesterday" which is confusing.
Whereas if the latest message is either of today/yesterday then the timestamp indicates today/yesterday properly.
Description
Attaching a screenshot of the issue.
Note: removed messages and contacts for privacy from the screenshot.
Steps to reproduce
Open a channel which has messages from a few days ago.
Expected behavior
Timestamp should not indicate "yesterday" if message is older than 1 day.
Actual behavior
Additional Information
The text was updated successfully, but these errors were encountered: