Chat refreshing when I select the app tab
I'll screencast it soon, I always forget to launch the screen recorder before accessing the tab, but it is a VERY annoying issue. If I let the tab dormant for some time, say 30 minutes, when I access it again the circle I was on refreshes. On accessing the tab, I see the conversation so I start reading it or writing what I had to say, or even selecting the Circle I wanted to go to, and then the app freezes a bit a reloads the current circle's chat. In terms of user experience it is really bothering. I'd make it a priority.
I finally caught it on camera, so here it is:
Link issues together to show that they're related. Learn more.
Activity
@alexbourlier is it the same as what you were experiencing in https://git.startinblox.com/applications/sib-app/issues/412 ? @jbpasquier we are still with auto-reconnect set to true?
- Owner
Auto reconnect is set to true and need to stay on this parameter, it's
clear_messages_on_reconnection
which is now false.@deleolajide Any idea why we still face this behavior?
- Author Maintainer
- Guest
Any idea why we still face this behavior?
If the connection is lost, auto_reconnect would signal a re-connection and that can cause the circle chat history to refresh. I would need to reproduce to be absolutely sure.
- Author Maintainer
I finally thought about recording my screen before accessing the tab. I literally failed doing that for 9 days in a row... Anyway, the GIF is in the description of the issue now.
- Author Maintainer
To me, this is the most painful issue at the moment regarding the chat. Second most painful would be https://git.startinblox.com/components/sib-chat/issues/99
- Please register or sign in to reply
- Alex changed the description
changed the description
- Rachel mentioned in issue management/sip-app-management#10 (closed)
mentioned in issue management/sip-app-management#10 (closed)
- Rachel changed milestone to %Chat (not in dedicated repo)
changed milestone to %Chat (not in dedicated repo)
- Owner
@deleolajide Could you estimate this one with a workaround like "When I re-access my tab, messages are hidden and I see a loader the time of refreshing, then I get back to the chat"?
- Rachel assigned to @deleolajide
assigned to @deleolajide
- Guest
This is a browser feature
When you have a lot of tabs open, Chrome can be really slow. ... By default, if it's using a lot of memory, Chrome purges the contents of some background tabs from RAM to conserve system resources. When you click back onto those tabs, the browser has to reload them because they have been erased from memory
Firefox https://www.askvg.com/fix-mozilla-firefox-automatically-suspends-tabs-and-reloads-when-you-visit/
Chrome https://www.guidingtech.com/stop-chrome-reloading-tabs-automatically-switching/
- Owner
No, the issue is about converse refreshing only, not the whole page. In fact, if the whole page would refresh, this would "solve" the problem.
- Guest
Part of conserving system resources is to drop network connections. That is why mobile applications use push notification when the app goes into background. I am not sure that that is the case here, but if it is, Converse will not refresh the whole page, but reconnect and reload the chat history.
Could you estimate this one with a workaround like "When I re-access my tab, messages are hidden and I see a loader the time of refreshing, then I get back to the chat"?
I am not sure I fully understand what I am estimating for.
- Owner
When we go back on the tab today, you still see the page as it was before, you can do whatever you want like scroll to read messages or start typing a message. Then, after 3-5 seconds, the chat disappear and an actualized one come in place, with eventually new messages on if any and you'll lose your message or the position where you're reading. We're missing at least a loader to tell the user that they have to wait, that we need to refresh the connection.
- Author Maintainer
I realize that I haven't faced this behaviour for some time now. Might just be me though, maybe this UX bug is still here.
- Guest
Then, after 3-5 seconds, the chat disappear
This might be another reason to consider using websockets instead of bosh. Until Converse detects the disconnect, there is not much we can do.
We're missing at least a loader to tell the user that they have to wait,
In SiB Chat settings, we are setting
auto_reconnect
to true. If set to false, Converse will triggers a 'disconnected' event which can be used in the SiB Chat UI to display a message and then call converse.api.connection.reconnect()
@alexbourlier are you still experiencing it?
- Author Maintainer
No I don't
- Alex closed
closed