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
When replying in a thread from a parent MessageListView, sending a reply resets the scroll position of the parent MessageListView to the bottom, so users lose their place in the chat after replying. I'm guessing a fix for this would be to not automatically scroll to the bottom when a thread reply is added.
Steps to reproduce
1. Override threadBuilder with your own ThreadPage implementation
2. Find a chat with a bunch of messages in it and scroll up to the top
3. Long press one of the first messages and tap on Thread Reply
4. Add a reply to the thread in ThreadPage
5. Exit ThreadPage and notice how the chat is now at the bottom and you've lost your place in the chat message list.
Supporting info to reproduce
No response
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
jagged91
changed the title
Replying in a thread scrolls the main MessageListView to the bottom
Users lose their place in the conversation after replying in threads.
Sep 15, 2021
Which packages are you using?
stream_chat_flutter
On what platforms did you experience the issue?
iOS, Android
What version are you using?
2.2.1
What happened?
When replying in a thread from a parent MessageListView, sending a reply resets the scroll position of the parent MessageListView to the bottom, so users lose their place in the chat after replying. I'm guessing a fix for this would be to not automatically scroll to the bottom when a thread reply is added.
Steps to reproduce
Supporting info to reproduce
No response
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: