noVNC/core
Pierre Ossman dbd519558c Initiate connection from RFB constructor
We need to do this in order to safely attach to existing WebSocket
objects. There may be message events already pending so we must set up
our event handlers before returning.

This means we will now throw errors instead of generating "disconnect"
events on problems as the caller no longer has the opportunity to set up
event handlers.

This might have been the correct approach from the start as it mimics
how e.g. the WebSocket constructor works.
2021-04-18 14:27:57 +02: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 Initiate connection from RFB constructor 2021-04-18 14:27:57 +02:00
websock.js Don't fake open events in Websock 2021-04-18 14:26:30 +02:00