RocketChat / RocketChat/Rocket.Chat
Fix: The pointer don't scrolls automatically to the new line when Shift+Enter is pressed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
The pointer don't scrolls automatically to the new line when Shift+Enter is pressed even though the pointer is in new line.
This happens only when the Max Message box height is reached. Else it works fine.
Steps to reproduce:
Try Writing multiline message on Rocket Chat web view.
As shown in the video below.
Actual behavior:
https://github.com/user-attachments/assets/eb794ce6-6a90-42d9-8c7f-1e98191c0083
Expected behavior:
https://github.com/user-attachments/assets/2171ecd1-5124-4a4c-8c8f-96477e897422
--The code is complete, will add a PR in a couple of minutes.
Server Setup Information:
- Version of Rocket.Chat Server: 7.5.0-develop
- License Type:
- Number of Users:
- Operating System: Ubuntu 24.04
- Deployment Method:
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version: \v22.13.1
- MongoDB Version:
Client Setup Information
- Desktop App or Browser Version: Brave
- Operating System: Ubuntu 24.04
Additional context
Relevant logs:
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 Rocket.Chat web view: enter a multiline message, press Shift+Enter after the maximum message-box height is reached, and compare the pointer position with the attached videos. Done means the pointer automatically scrolls to the new line in this case, while existing behavior remains unchanged when the height limit is not reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100