You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observe that when you press Enter, the textbox is cleared, but the message never actually gets sent.
What is the expected behaviour?
The message should either remain in the textbox and an error should be displayed, or it should be sent to the other party. The current behavior causes messages to be dropped silently, which is not a good experience, particularly if the user has just typed a lengthy message.
Refreshing and letting Wire load again causes sending to work properly, so this seems to be a reliable workaround.
Which browser are you using?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0
Installed browser addons
h264ify
Old Reddit Redirect
Reddit Enhancement Suite
uBlock Origin (I checked and it's not blocking anything on app.wire.com)
Video Quality Settings for YouTube
Other comments
I am not sure if this behavior is reproduceable in Chrome on the same machine or not. I normally use Firefox for performance/memory reasons. Also, this only started occuring after the recent update to the web app which made messages animate upwards smoothly when a new one appears, if that helps with bisecting.
The text was updated successfully, but these errors were encountered:
Your Account Type
What steps will reproduce the problem?
What is the expected behaviour?
The message should either remain in the textbox and an error should be displayed, or it should be sent to the other party. The current behavior causes messages to be dropped silently, which is not a good experience, particularly if the user has just typed a lengthy message.
Refreshing and letting Wire load again causes sending to work properly, so this seems to be a reliable workaround.
Which browser are you using?
Installed browser addons
Other comments
I am not sure if this behavior is reproduceable in Chrome on the same machine or not. I normally use Firefox for performance/memory reasons. Also, this only started occuring after the recent update to the web app which made messages animate upwards smoothly when a new one appears, if that helps with bisecting.
The text was updated successfully, but these errors were encountered: