send() could be more precise

[domenic]

What is the issue with the WebSockets Standard?

Consider code such as the following:

const bytes = new Uint8Array([0x01]);
webSocket.send(bytes);
bytes[0] = 0x02;

Is 0x01 sent, or 0x02?

What about

const bytes = new Uint8Array([0x01]);
webSocket.send(bytes);
bytes.buffer.transfer();

?

Probably the desired answer is that we snapshot the bytes the moment they are fed to the send() method? If so, the spec should use https://webidl.spec.whatwg.org/#dfn-get-buffer-source-copy to be explicit.

[nektro]

Probably the desired answer is that we snapshot the bytes the moment they are fed to the send() method?

as a dev, this is what i think would lead to least amount of confusion

[ricea]

I was surprised this wasn't already specified! In practice, Blink copies the data as you'd expect.

There's also a subtle spec error hiding here, in that the definition of the send() method delegates to the send a WebSocket Message algorithm from RFC6455, but that's actually a blocking algorithm. So the WebSocket spec should say "In parallel, " there somewhere.