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
Messages appear with timestamps in order chronologically regardless of whether they originated in Slack or Matrix.
Actual Behavior
When viewing on Matrix (Element on macOS) and with delays on messages from Slack appearing in Matrix, once those delayed Slack messages make it to Matrix they appear with odd timestamps and appearing before a threaded Matrix message that has a timestamp before the Slack messages. I know, this sounds weird and probably confusing but check out the screenshot below to get a better sense of the issue.
Steps to Reproduce
No response
Environment
macOS 14.1.1
Element 1.11.50
Screenshots
My threaded response at the bottom of this screenshot was within Matrix and appeared first but then messages from Slack started eventually piping in above it but with timestamps after my Matrix message. An odd user experience all around.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Expected Behavior
Messages appear with timestamps in order chronologically regardless of whether they originated in Slack or Matrix.
Actual Behavior
When viewing on Matrix (Element on macOS) and with delays on messages from Slack appearing in Matrix, once those delayed Slack messages make it to Matrix they appear with odd timestamps and appearing before a threaded Matrix message that has a timestamp before the Slack messages. I know, this sounds weird and probably confusing but check out the screenshot below to get a better sense of the issue.
Steps to Reproduce
No response
Environment
macOS 14.1.1
Element 1.11.50
Screenshots
My threaded response at the bottom of this screenshot was within Matrix and appeared first but then messages from Slack started eventually piping in above it but with timestamps after my Matrix message. An odd user experience all around.
Additional Context
No response
The text was updated successfully, but these errors were encountered: