Forum Discussion
Problems with Websockets in Version 81.0.381.0
zawarski We're sorry to hear that you're encountering that, and thanks for letting us know! If you haven't yet, can you please try it on Chrome Canary? (It corresponds the most closely with Edge Canary, so if there's a bug in Chrome's, it may be in ours too.) If it isn't occurring there too, I will pass this directly to the correct product team.
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
Deleted I downloaded Canary Chrome, like you suggested, and the problem is happening there too. I am using Primus (https://github.com/primus/primus) as the Websocket server. Don't know if I, or it, is doing something "non-kosher" and the Chromium engine is now sensitive to it. or if the problem is in Chromium.
Thanks for the heads up.
Rob Zawarski
zawarski Thanks for doing some digging, Rob. Whenever you're noticing an issue in both Edge and Chrome (especially in corresponding builds/channels,) that usually means it originated in Google's side of the Chromium Project, and thus, also happened to get incorporated into Edge's code. However, I want to make sure that we address this to our fullest capacity, so I will pass this along.
Please let us know if you encounter anything similar!
Fawkes (they/them)
Project & Community Manager - Microsoft Edge