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
The "Seen by ..." / read receipt icons show alongside the last seen message, but if the message is long (e.g. a reply) they show at the top of that message:
This can sometimes be confusing, especially with a wide screen, as it looks as if they haven't seen the big message when they have.
The confusion is made worse by the visual joining of multiple consecutive messages from the same person, as the separation of the messages isn't visible unless you move the mouse over it, so there is sometimes no visual cue exactly how far through that user's text people have really seen.
it would be better to show these icons aligned with the bottom of the message, as that is the actual separation of seen/unseen.
Steps to reproduce
send (multiple consecutive) long message (e.g. a long reply) in room with others
icons should move to bottom of last message seen as people see the messages
Version information
Platform: desktop
OS: Arch Linux
Version: element-desktop-1.7.10-1
The text was updated successfully, but these errors were encountered:
Description
The "Seen by ..." / read receipt icons show alongside the last seen message, but if the message is long (e.g. a reply) they show at the top of that message:

This can sometimes be confusing, especially with a wide screen, as it looks as if they haven't seen the big message when they have.
The confusion is made worse by the visual joining of multiple consecutive messages from the same person, as the separation of the messages isn't visible unless you move the mouse over it, so there is sometimes no visual cue exactly how far through that user's text people have really seen.
it would be better to show these icons aligned with the bottom of the message, as that is the actual separation of seen/unseen.
Steps to reproduce
Version information
The text was updated successfully, but these errors were encountered: