Forum Discussion
zawarski
Jan 14, 2020Copper Contributor
Problems with Websockets in Version 81.0.381.0
The same site that I can successfully use a websocket connection with real Chrome Version 79.0.3945.117 (Official Build) (64-bit) and Firefox Versin 72.0.1 (64-bit) connects with Edge Chrome Version ...
Eric_Lawrence
Microsoft
Jan 16, 2020zawarski If there's a public site and repro steps, I'm happy to do the bisect to figure out when exactly this broke in Chromium, so the bug can either be fixed in the browser or on the site before 81 goes to Stable.
If you use edge://net-export, there may be interesting details in the generated log file.
- Eric_LawrenceJan 21, 2020
Microsoft
I believe this is a small bug in the DevTools, not in WebSocket. See https://bugs.chromium.org/p/chromium/issues/detail?id=1041752#c10
- zawarskiJan 23, 2020Copper Contributor
Eric_Lawrence Not *that* small of a bug. It makes it impossible to monitor websocket traffic. But yes, that's it. Thanks for the reply.
- Eric_LawrenceJan 23, 2020
Microsoft
Small, in the sense that fixing it required that I delete one word from the code. The fix was checked in immediately.