You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched open and closed issues for duplicates
Bug description
Some of the timestamps in the message bubbles stop to get updated after a while. Same goes for the timestamps in the conversations list, altough they don't fail necessarily the same way. (e.g. the conversations list could show "53 min" and the bubble "2 hours ago" for the same message)
After I restart the app all timestamps are fixed.
This issue has been reported before (#460) but has been closed since, so I figured it would be helpful to report it again.
Possibly related: #812
Steps to reproduce
have a conversation
Actual result: Some timestamps fail to update. Expected result: The timestamps should stay updated.
Screenshots
Platform info
Operating System: Windows 10 Browser: Chrome 51 Signal version: 0.17.1
The text was updated successfully, but these errors were encountered:
TimestampView's getRelativeTimeSpanString called moment() twice while calculating the timeout. If there was a minute/hour/day wrap between these 2 calls, the calculated delay was 0 and thus no timer was scheduled, since if (this.delay) evaluated to false.
Fixes: signalapp#857, signalapp#460
// FREEBIE
Bug description
Some of the timestamps in the message bubbles stop to get updated after a while. Same goes for the timestamps in the conversations list, altough they don't fail necessarily the same way. (e.g. the conversations list could show "53 min" and the bubble "2 hours ago" for the same message)
After I restart the app all timestamps are fixed.
This issue has been reported before (#460) but has been closed since, so I figured it would be helpful to report it again.
Possibly related: #812
Steps to reproduce
Actual result: Some timestamps fail to update.
Expected result: The timestamps should stay updated.
Screenshots
Platform info
Operating System: Windows 10
Browser: Chrome 51
Signal version: 0.17.1
The text was updated successfully, but these errors were encountered: