RocketChat / RocketChat/EmbeddedChat
Bug: Returning from a thread view doesn't show the previous scroll state.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 165
- Forks
- 381
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Description:
When viewing a message thread and then returning to the main chat using the top-left back arrow, the message list jumps to very old/top messages instead of returning to the previous position in the main conversation.
Steps to reproduce:
- Open EmbeddedChat in a channel with enough history to scroll.
- Scroll in the main chat away from the latest messages.
- Open a message thread from any message.
- Click the top-left back arrow to close the thread and return to main chat.
Expected behavior:
Returning from thread view should restore the previous main-chat scroll position (or at least keep the user near where they were before opening the thread), without jumping to old/top messages.
Actual behavior:
After closing the thread, the main chat shows very old messages near the top of history instead of the previous position. In some cases, this also triggers loading older messages immediately.
https://github.com/user-attachments/assets/ff4bb1b3-7f28-4742-bbae-908289a2a522
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in EmbeddedChat with a scrolled conversation, then inspect the thread view and top-left back navigation where the main chat is restored. Done means returning from a thread preserves the previous main-conversation scroll position without jumping to old messages or immediately loading older history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100