mirror of
https://github.com/RetroShare/RSNewWebUI.git
synced 2026-09-14 11:05:47 +05:00
00459bbbcb
rsJsonApiRequest hands the callback the HTTP status, not the answer, and the button read that as "the tunnel is closed": any reply at all, including one that says nothing was closed, ended the conversation on screen. The core does report it, in retval, so that is what is read now, and the ended card says which of the two happened -- closed on request, or already gone before the click. The status poll had the same deafness and is what let it happen. Once a tunnel is gone from the core -- died of inaction, closed by the peer -- getDistantChatStatus answers false, and the poll only ever looked at the branch where it answers true. So the last known status stayed on screen for good: a conversation whose tunnel had been dead for a while kept its green dot and its "You can talk", and Leave Chat then had, quite correctly, nothing to close. Two consecutive false answers now end the conversation, with a line saying so, which is the state the user was in. Needs the libretroshare side to be meaningful: fix/distant-chat-close-keeps-contact makes closeDistantChatConnexion report whether it closed anything, and drop the distant chat contact it used to leave behind. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| boards | ||
| channels | ||
| chat | ||
| config | ||
| files | ||
| forums | ||
| network | ||
| people | ||
| scss | ||
| home.js | ||
| jdenticon.js | ||
| login.js | ||
| main.js | ||
| mithril.js | ||
| rswebui.js | ||
| statusbar.js | ||
| widgets.js | ||