RocketChat / RocketChat/Rocket.Chat
Inconsistent scrolling after jumping to a search result
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When jumping to an old message after searching, scrolling further back in history makes it jump to days later. Making it impossible to keep on scrolling back.
This happens both on the desktop app as in the browser
Steps to reproduce:
- search for a string in the past
- jump to a old match
- try scrolling from that back further in history for a while.
- it seems when it has to load in older messages, it suddenly jumps forward.
Expected behavior:
Being able to keep on scrolling back in history after jumping to a found line in a search action.
Actual behavior:
While scrolling back you get thrown forward in time.
Server Setup Information:
- Version of Rocket.Chat Server: 7.3.1
- License Type: Community
- Number of Users: 3
- Operating System: official docker image
- Deployment Method:
- Number of Running Instances:
- NodeJS Version: official docker image
- MongoDB Version: 6.0.20
Client Setup Information
- Desktop App or Browser Version: 4.1.2 and Brave 1.75.175
- Operating System: NixOS 24.11
Contributor guide
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 the browser or desktop client using the four listed steps: search for an old message, jump to a match, and continue loading older history. Trace the search-result jump and history-loading behavior; done means scrolling backward remains in older history without jumping forward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100