network.websocket.timeout.ping.response too low
Categories
(Core :: Networking: WebSockets, defect, P3)
Tracking
()
People
(Reporter: davidj, Unassigned)
Details
(Whiteboard: [necko-triaged])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36
Steps to reproduce:
- Browse to https://www.websocket.org/echo.html
- Turn off wifi for 10 seconds.
- Turn wifi back on.
Actual results:
Websocket disconnected.
Expected results:
Websocket should have remained connected. There is no disconnect on Chrome. Firefox disconnects after 10 seconds by default (network.websocket.timeout.ping.response) which is too short for temporary network glitches. If I turn off my wifi and turn it back on again, it generally takes about 15 seconds to reconnect on my macbook pro.
|
||
Comment 1•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #1)
The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•5 years ago
|
Description
•