RocketChat / RocketChat/Rocket.Chat

Reply button in pinned message list has no effect

Open
#25,597 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area: ui/ux type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Pressing the blue "Reply" Button in the list of pinned messages has no effect, pressing "Jump to Message" and then "Reply" on the message in the channel area works.

Steps to reproduce:

image

image

Expected behavior:

The replies of the pinned message open and I can write a reply

Actual behavior:

Nothing happens when pressing Reply

Server Setup Information:
  • Version of Rocket.Chat Server: 4.7.2
  • Operating System: Debian Bullseye
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: wiredTiger (oplog Enabled)
  • NodeJS Version: v14.18.3
  • MongoDB Version: 4.2.19
Client Setup Information
  • Desktop App or Browser Version: chromium 101.0.4951.64 (amd64)
  • Operating System: Arch Linux
Relevant logs:

No relevant log messages

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 Reply action from the pinned message list, then compare it with the working Jump to Message and Reply flow in the channel area. Done means the pinned message opens its replies and allows composing a reply without errors; verify the behavior in the reported browser setup.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.