Expected behavior
When the client tab becomes inactive, it should not adapt the network buffer because of the tab's low processing priority.
Actual behavior
When the client tab becomes inactive, it increases the network buffer because of the tab's low processing priority. This causes unnecessary delays.
Reproduction steps
Go to /client.
Start a marble race.
Go to a different tab in the same browser window for ~30 seconds.
Expected behavior When the client tab becomes inactive, it should not adapt the network buffer because of the tab's low processing priority.
Actual behavior When the client tab becomes inactive, it increases the network buffer because of the tab's low processing priority. This causes unnecessary delays.
Reproduction steps
/client
.Platform OS: Windows 10 Browser version: Firefox Developer Edition 68.0b11 (64-bit) Build version: v1.2.0
Related issues Might be related to #206