Show connection error message immediately, also during reconnect #2138
Conversation
As catchup sync can take quite some time (maybe temporarily even slower with LL) it can be confusing when you come back to riot after a couple of days and you only see old messages while the first sync is running. If riot didn't get the time to fail /sync 3 times (like when sleeping your laptop), it won't show you anything to indicate your timeline is behind and its reconnecting. This is probably not the best way to deal with this, as in the laptop wakeup scenario, you might as well have 0 failed syncs but still catchup takes minutes. Looking at how much time there was between the last and new sync might be better, but this sort of does the job for now
There was a problem hiding this comment.
The reason for having reconnecting is that the nature of HTTP is that sometimes connections will drop and we'll have to retry, but that's not a problem.
I thought we had the spinner at the bottom when trying to sync, indicating that we're trying to fetch new messages?
|
@dbkr this is what @ara4n also thought, and that since LL it doesn't show anymore. I just went over it again and can't figure out how that would have ever worked. I guess a better fix would be to also show the spinner on |
|
Closed this in favor of matrix-org/matrix-js-sdk#702 |
As catchup sync can take quite some time (maybe temporarily even slower with LL)
it can be confusing when you come back to riot after a couple of days and you only see old messages while the first sync is running. If riot didn't get the time to fail /sync 3 times (like when sleeping your laptop), it won't show you anything to indicate your timeline is behind and its reconnecting.
This is probably not the best way to deal with this, as in the laptop wakeup scenario, you might as well have 0 failed syncs but still catchup takes minutes. Looking at how much time there was between the last and new sync might be better, but this sort of does the job for now
Addresses item 6 (We no longer show a spinner when recovering after losing connectivity) of element-hq/element-web#7182