forked from KickTalkOrg/KickTalk
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Description
When a user types content in the chat input and then clicks the reply button on a message, the pre-typed content is not sent as a reply when Enter is pressed. Only subsequent messages typed after clicking reply are treated as replies.
Steps to Reproduce
- Type a message in the chat input (e.g., "Hello world")
- Click the reply button on any message in the chat
- Press Enter to send the message
- Expected: "Hello world" should be sent as a reply to the selected message
- Actual: "Hello world" is sent as a regular message or not sent at all
Root Cause
React state updates are asynchronous. When the reply button is clicked, setReplyInputData(data) is called, but if the user immediately presses Enter, the replyInputData state might still be null due to the async update timing.
Impact
- Users cannot efficiently reply with pre-typed content
- Confusing UX where reply behavior seems inconsistent
- Workflow disruption for fast typists
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working