Tim Stableford ef27628c6d Fixed a race condition when attaching to an existing socket ... This is an error that presents itself with RTCDataChannel's, I suspect this could not happen with a pre-existing WebSocket. If the remote connection creates a data channel then the local (VNC) side gets a channel created callback. It may also be the case that in that very same tick the socket is also opened and buffered data received. This meant that (in my tests) about 1/3 of the time noVNC would fail to respond to the initial message from the server because it was received and subsequently not handled during that initial tick. Also made the documentation reflect this new behaviour and document the existing behaviour.		2021-03-30 14:32:04 +01:00
..
decoders	Handle empty rects in RAW decoder as well	2020-09-07 12:58:52 +02:00
input	chore: sync with W3C documentation	2020-12-22 10:50:23 +01:00
util	Remove createEvent() fallbacks	2020-12-07 10:10:53 +01:00
base64.js	Standardize on camelCase in Base64	2020-05-31 23:37:29 +02:00
deflator.js	Add camelCase rule to eslint	2020-05-31 23:37:29 +02:00
des.js	Convert DES into a class	2019-02-26 23:53:43 +02:00
display.js	Remove createImageData() fallback	2020-12-07 10:10:53 +01:00
encodings.js	Add extended clipboard Pseudo-Encoding	2020-02-18 09:32:36 +01:00
inflator.js	Add camelCase rule to eslint	2020-05-31 23:37:29 +02:00
rfb.js	Fixed a race condition when attaching to an existing socket	2021-03-30 14:32:04 +01:00
websock.js	Added support for RTCDataChannel	2021-03-04 18:55:06 +00:00