RocketChat / RocketChat/Rocket.Chat

Improvement: Toggle User Info when tapping the participant name in 1:1 DM foreword

Open
#40,514 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

In a 1:1 direct message room, the room foreword shows: “You have joined a new direct message with ”. The is rendered as a clickable link (Tag with href pointing to the same DM route, e.g. /direct/<username>).

When the user is already inside that DM, clicking the name re-navigates to the current room. That re-triggers the room open flow and causes visible flickering (and unnecessary navigation), instead of doing something useful (e.g. opening User Info or being a no-op).

Steps to reproduce:
  1. Log in as user A.
  2. Open a 1:1 Direct message with user B (only you and B in the room).
  3. Scroll to the top of the message list so the room foreword is visible (“You have joined a new direct message with …”).
  4. Click the clickable username for B in the foreword.
    (Optional) Click the same username again and observe repeated flicker.
Expected behavior:
  • Clicking the username in the foreword should not re-navigate to the same DM when already in that room (no flicker).
  • Preferably, the control should toggle the same User Info / contextual panel as the room header flow (consistent with opening User Info for the other participant in a 1:1 DM), or at minimum no-op when already on the target room.
Actual behavior:
  • Each click performs navigation to the same DM URL / room open sequence.
  • The chat UI flickers (brief reload / re-mount style behavior) on each click.
  • No User Info is opened from that control in 1:1 DM.

https://github.com/user-attachments/assets/546e2e82-39e1-497b-8e8a-49273a151262

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 locating the 1:1 DM room foreword entry point and its clickable participant name, then compare it with the room header's User Info flow. Reproduce the current same-room navigation and verify that clicking the name opens User Info or at least avoids re-navigation and flicker.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.