fix: unread underlay display for own messages#3145
Merged
Conversation
Contributor
SDK Size
|
isekovanic
approved these changes
Jul 3, 2025
Contributor
|
🎉 This PR is included in version 8.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lately, the unread underlay was not getting displayed for own messages, which shouldn't be the case if we are allowing the mark as unread action for the own messages sent in the message list. This change has been reverted from #3119, and the visibility of the unread label when there are long messages when a new message is sent is fixed, where the event is handled. This is to cover the cases for display of unread underlay for own messages in certain cases, and the unread count increased to one if the condition fixed was met.