-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show the chat box even before the counterparty is 'online'? #70
Comments
Hey @dbolser Thanks a lot for the input and ideas!
This is exactly how it works, right? You just follow the
Everything except the chat itself are HTTP requests that your browser is sending every X seconds. You probably won't miss it if you are looking at your browser. But there might be extra features that could be added to make sure people knows they are online and fine! |
Got it! |
Hey @dbolser The new chat upgrade is very explicit about who is connected / disconnected. Two flags show on top "You: connected", "Peer: disconnected", as well as avatars will show a green or red dot over themselves. If the connection drops, the chat websocket will keep trying to reconnect until successful. In addition, the "Send" button will be disabled if you are not connected and will display a "Connecting..." helper text below it. The chat will however not be shown until both users have finished the step before (has to be at Fiat exchange step). I believe this fixes any reasonable concern about whether you or your counterpart are connected. If nothing comes up will close this issue in a few days. |
Is your feature request related to a problem? Please describe.
As a noob, I'm not sure where the chat box should appear / if hte site may be broken / if I@m supposed to be doing something, etc.
Describe the solution you'd like
If the chat box appeared with teh animated text (waiting for counterparty...) I would know the state wasn't 'on me' and that I'm waiting for someone in the background.
Describe alternatives you've considered
Additional context
Meh
The text was updated successfully, but these errors were encountered: