RocketChat / RocketChat/Rocket.Chat

"Jump to Message" does not work in embedded layout

Open
#26,523 0 comments 1 reaction 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

Description:

In RocketChat, a # with the message ID can be appended for the screen to directly jump to a message. This does not work when passing ?layout=embedded

Steps to reproduce:
  1. Go to a direct message of your choice, like https://<your-rocketchat-instance>/direct/<username>
  2. Append a message ID to the URL, such as #<message-id>
  3. See the chat jump to the selected message
  4. Do the same in embedded mode, such as #<message-id>?layout=embedded and see that the chat no longer jumps to the message
  5. Do the same the other way around, such as ?layout=embedded#<message-id> and see that the embedded layout no longer works
Expected behavior:

Embedded layout should mirror the behaviour

Actual behavior:

Different behaviour between the two

Server Setup Information:
  • Version of Rocket.Chat Server: 4.8.2
  • Deployment Method: Docker
Client Setup Information
  • Desktop App or Browser Version: Chrome 103
  • Operating System: macOS

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

Start by reproducing the direct-message URLs with the message-ID hash and the embedded layout query parameter in both orders. Trace the client-side handling of the hash and embedded layout, then verify that embedded mode jumps to the selected message without preventing the layout from loading.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.