Hello,
When a web page uses a WebSocket connection to receive live data, that connection is closed after a few minutes when the tab is inactive. That causes my web app to miss critical information and prevents it from notifying the user appropriately.
How can I stop this? I want my connections to close when I say, not when the browser thinks it might not be needed anymore. It still is.
If this is about battery saving: Last time I looked into my desktop PC, it had no battery.
If this is about energy saving in general: I know how to handle the visibilitychange event and disable work that really isn't needed when the page is invisible. Closing the server connection is not on that list.
WebSocket is closed in an inactive tab
- ygoe
- Posts: 215
- Joined: November 10th, 2003, 2:51 pm
- Location: Germany
- Contact: