-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Threads: When read, doesn't leave Unreads filter view #7090
Threads: When read, doesn't leave Unreads filter view #7090
Comments
At random cases the fetcher predicate fetches data with |
I think it was because |
Reopening as the original fix was reverted in matrix-org/matrix-ios-sdk#1736. |
I don't understand why matrix-org/matrix-ios-sdk#1723 was reverted by matrix-org/matrix-ios-sdk#1736 ? Unread tabs list a lot of totally read rooms. If i locally reapply matrix-org/matrix-ios-sdk#1723 then unread tab only lists rooms with unread messages as attended. Please, reapply matrix-org/matrix-ios-sdk#1723 |
If I remember correctly, whilst the mentioned PR did fix the underlying bug, it completely changed the desired behaviour of the tab, which is to only show rooms with notifications, and not simply any room where the read marker isn't on the last event. This is why the bug still stands, it will need to be fixed some other way. |
@NicolasBuquet I have the same memories as Doug. |
Thank you for your comments. But to have a better understanding, what is the difference between a room with unread messages and a room with notifications? And, won't it be a good thing finally to be able to parametrize this filter on the Matrix SDK side? |
If you set a room's notification settings to Mentions and Keywords only, then it will have an unread message for you when someone sends a message of
|
@pixlwave Thank you for this explanation. It's clearer for me now. 🙏 |
I got a thread message in a room, once I read it and went to the Unreads tab the message is read but the room shows in the Unreads tab still
The text was updated successfully, but these errors were encountered: