Context
Emoji reactions are rendered in EmbeddedChat but clicking a reaction count does nothing — users cannot see who reacted, which is a standard expectation in Slack/Discord/RC web. The data exists on the server (RC REST endpoint GET /api/v1/chat.getReactions) but nothing surfaces it.
Feature description
When a user clicks a reaction bubble (e.g. ':thumbsup: 3'), open a small modal listing each emoji tab with the avatars+usernames of reactors. Matches Rocket.Chat web UX. Works for all message types already supporting reactions.
Value
Completes the reaction UX loop — users can audit who agreed/laughed/approved without leaving the chat. Low risk: purely additive, touches one isolated view, uses an existing RC REST endpoint with no WebSocket complexity.
Context
Emoji reactions are rendered in EmbeddedChat but clicking a reaction count does nothing — users cannot see who reacted, which is a standard expectation in Slack/Discord/RC web. The data exists on the server (RC REST endpoint GET /api/v1/chat.getReactions) but nothing surfaces it.
Feature description
When a user clicks a reaction bubble (e.g. ':thumbsup: 3'), open a small modal listing each emoji tab with the avatars+usernames of reactors. Matches Rocket.Chat web UX. Works for all message types already supporting reactions.
Value
Completes the reaction UX loop — users can audit who agreed/laughed/approved without leaving the chat. Low risk: purely additive, touches one isolated view, uses an existing RC REST endpoint with no WebSocket complexity.