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
Where are you starting? What can you see?
I open the desktop client, read all threads and messages, but the threads icon is still with a 'button' on it, showing there are more messages to be read, despite I read them all. Three times :)
What do you click?
Normal navigation inside the app in the threads.
More steps…
Sometimes app restart helps. But this time it doesn't. Nor even clear cash and restart app does.
Outcome
What did you expect?
Messages to be marked as read when they are read.
What happened instead?
Client shows me there are still things to read.
Operating system
MacOS
Application version
Version 1.11.29 (1.11.29)
How did you install the app?
Official site
Homeserver
1.64.0; but I believe it was the same with 1.63.0
Will you send logs?
No
The text was updated successfully, but these errors were encountered:
go inside of the thread not via the thread icon at the top right side, but from the thread footer under the original message - then Element immediately mark the messages as read
Steps to reproduce
Where are you starting? What can you see?
I open the desktop client, read all threads and messages, but the threads icon is still with a 'button' on it, showing there are more messages to be read, despite I read them all. Three times :)
What do you click?
Normal navigation inside the app in the threads.
More steps…
Sometimes app restart helps. But this time it doesn't. Nor even clear cash and restart app does.
Outcome
What did you expect?
Messages to be marked as read when they are read.
What happened instead?
Client shows me there are still things to read.
Operating system
MacOS
Application version
Version 1.11.29 (1.11.29)
How did you install the app?
Official site
Homeserver
1.64.0; but I believe it was the same with 1.63.0
Will you send logs?
No
The text was updated successfully, but these errors were encountered: