RocketChat / RocketChat/EmbeddedChat
Incorrect render order for quoted messages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 165
- Forks
- 381
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Quoted message text renders before quote UI, causing confusing message sequence
While reviewing the quote message flow, I noticed a UI inconsistency in how quoted messages are rendered.
Currently, when a message is quoted, the message text is rendered before the quote UI block, which can be confusing when multiple messages from the same user appear in sequence.
In the official Rocket.Chat app, the quote UI is rendered first, followed by the message text, resulting in a clearer and more intuitive message flow.
Steps to reproduce:
- Send a message with some text.
- Quote that message.
- Send the quoted message.
- Observe the rendered output in the message list.
Expected behavior:
The quote UI block should appear first, followed by the message content, maintaining a clear UI and consistent visual hierarchy, similar to how quoting is handled in the Rocket.Chat.
Actual behavior:
The quoted text appears before the quote UI, which makes it look like part of the normal message flow and can be confusing when messages are displayed in sequence from the same user.
Contributor guide
No contributing guide indexed for this repository
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 tracing the quoted-message rendering from the message list and identify where the quote UI block and message content are ordered. Reproduce the quoted-message flow described in the issue, then verify that the quote UI appears before the message text and that the sequence remains clear for consecutive messages from the same user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100