That tab refresh occurs when more than half of the relays are disconnected (this means not to work correctly) when you come back to the nostter tab.

This behavior which depends on browser WebSocket is currently by design as I haven't found a better way to do it.