bug: messageInput autocomplete for emotes (e.g `<3`) sends the message without cleaning the input state
kennyvallejodev opened this issue · 2 comments
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to getstream-chat-demo-team
- Click on Message Input
- Type
<3and press enter - See error
- You will see how is send
<3as a plain text - You will also see how the input value is now
❤️<
(Looks like after pressing enter, is now replacing <3 with the actual ❤️)
- You will see how is send
not only that, this also works the same for the mentions, if you mention someone that has for example <3 at the end of the name (e.g Kenny <3) it will be bugged as well and when you press enter, the mention is first send as a plain text (with no mention interaction) and the input state will remain having the value.
Expected behavior
A clear and concise description of what you expected to happen.
Do the replace of the emotes once the message is send? Send the message properly (in the case of mentions) and not as a plain text.
Screenshots
If applicable, add screenshots to help explain your problem.
Screen.Recording.2024-03-08.at.8.50.34.AM.mov
Package version
- stream-chat-react: 11.12.0
- stream-chat-css: (no idea- using just stream-chat-react and stream-chat)
- stream-chat-js: 8.22.0
Desktop (please complete the following information):
- OS: [e.g. iOS] MacOS
- Browser [e.g. chrome, safari] Chrome
- Version [e.g. 22] 122.0.6261.112
Smartphone (please complete the following information):
- Device: [e.g. iPhone6] N/A
- OS: [e.g. iOS8.1]N/A
- Browser [e.g. stock browser, safari]N/A
- Version [e.g. 22]N/A
Additional context
Add any other context about the problem here.
Thanks for the report @kennyvallejodev! This has been fixed and released in v11.12.1.
Thanks for the report @kennyvallejodev! This has been fixed and released in v11.12.1.
Thank you for taking the time on fixing this one!