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 problem happens on Element Web (but not on Element Android) whenever someone replies to a reply.
Outcome
The UI is really weird and confusing because it mentions two different people, which makes it hard to know who's being replied to; it also formats their names differently, which adds to the confusion. Here's an example:
I think the UI should be simplified and only mention one person, which should be the person being replied to. Like this:
But if you think it's important to also show the other person, I think that both people should be mentioned in the same line. Like this:
Operating system
Fedora
Browser information
Firefox
URL for webapp
develop.element.io
Homeserver
envs.net
Will you send logs?
No
The text was updated successfully, but these errors were encountered:
It seems you're not the only one to have come across this bug, as it's been reported previously. I'm going to close this issue now so we can focus on the older issue. Please watch, vote or comment on that issue if there is any additional information you can provide.
Steps to reproduce
The problem happens on Element Web (but not on Element Android) whenever someone replies to a reply.
Outcome
The UI is really weird and confusing because it mentions two different people, which makes it hard to know who's being replied to; it also formats their names differently, which adds to the confusion. Here's an example:
I think the UI should be simplified and only mention one person, which should be the person being replied to. Like this:
But if you think it's important to also show the other person, I think that both people should be mentioned in the same line. Like this:
Operating system
Fedora
Browser information
Firefox
URL for webapp
develop.element.io
Homeserver
envs.net
Will you send logs?
No
The text was updated successfully, but these errors were encountered: