WebAssembly WebSockets multi-buffer sends don't work

[BrennanConroy]

Using 5.0 WebAssembly with WebSockets, multi part sends are not handled correctly.

Only the final send with endOfMessage == true is actually sent because the writtenBuffer variable is never used.

runtime/src/libraries/System.Net.WebSockets.Client/src/System/Net/WebSockets/BrowserWebSockets/BrowserWebSocket.cs

Line 366 in 1923bba

MemoryStream writtenBuffer = _writeBuffer;

It would be nice to get this fixed for 5.0. I would have tried fixing it, but building WASM isn't super easy it seems.

@kjpou1 @marek-safar

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Details

---

Issue meta data

Issue content:	Using 5.0 WebAssembly with WebSockets, multi part sends are not handled correctly. Only the final send with endOfMessage == true is actually sent because the writtenBuffer variable is never used. runtime/src/libraries/System.Net.WebSockets.Client/src/System/Net/WebSockets/BrowserWebSockets/BrowserWebSocket.cs Line 366 in 1923bba MemoryStream writtenBuffer = _writeBuffer; It would be nice to get this fixed for 5.0. I would have tried fixing it, but building WASM isn't super easy it seems. @kjpou1 @marek-safar
Issue author:	BrennanConroy
Assignees:	-
Milestone:	-

[marek-safar]

Building should be as easy as typing in ./build.sh -os browser -arch wasm in the root folder

[lewing]

This is unfortunate. The code gained extra buffering and broke functionally when it moved over from mono/mono

[BrennanConroy]

Fixed via #44611