RocketChat / RocketChat/Rocket.Chat

Omnichannel Livechat: New long replies scroll to the bottom instead of the top/start of the message

Open
#37,342 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

When an agent sends a long reply message in an active Omnichannel Livechat session (via the Agent interface), the chat window automatically scrolls to the bottom of the newly displayed message content instead of scrolling to the top/start of the long message. This forces the end-user (visitor) to manually scroll up to read the beginning of the agent's long response.

Steps to Reproduce:

Start a new Livechat session (as a visitor on the widget).

Accept the chat as an Agent in the Rocket.Chat interface.

Send a very long message (e.g., paste a text block exceeding 5-10 lines) from the Agent interface.

Observe the scroll position in the Visitor's Livechat widget view.

Expected Behavior: The chat widget should automatically scroll to the beginning (top) of the newly received long message, allowing the user to read the content sequentially from the start.

Actual Behavior: The chat widget automatically scrolls to the end (bottom) of the newly received long message. The user must manually scroll up to see the beginning of the message.

Environment Information:

Rocket.Chat Server Version: Version 7.10.0

Deployment Method: Docker

Browser used by Agent (to send the message): Chrome 141.0.7390.122

Operating System (Agent/Visitor): windows & ubuntu

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the visitor Livechat widget by sending a long message from the Agent interface, then trace the widget's incoming-message rendering and scroll handling. Verify the scroll position for long agent replies and add coverage if the relevant test area is found; done means the visitor can read a new long reply from its beginning without manually scrolling up.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.