Lars Ole Hurlen 49aa5b81c7 Detect RealVNC's RFB 5.0 Protocol Version ...

The RFB protocol specifies a max version of 3.8, but RealVNC likes to
increment their version when they add new features.  RealVNC 5.3 sends
"005.000" as the version string, since they've extended their
implementation upon RFB v3.8.  We can detect that, and just tell them we
only speak 3.8, instead of barfing on "005.000" as an invalid version.

2016-09-16 17:33:46 -04:00

..

assertions.js

Fix 'sent' assertion

2016-06-03 16:31:29 +02:00

fake.websocket.js

Use Typed Arrays for the send queue

2015-08-06 14:47:03 -04:00

input.html

Move input-related files into core/input

2016-09-16 15:49:52 -04:00

playback.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00

run_from_console.casper.js

Switch to PhantomJS 2.x for testing

2016-09-16 15:49:52 -04:00

run_from_console.js

Switch to PhantomJS 2.x for testing

2016-09-16 15:49:52 -04:00

run_from_console.zombie.js

Support Skipped Tests and Fix JSHint Issues

2013-12-17 17:56:18 -05:00

test.base64.js

Cleanup and Test: base64.js

2014-09-15 16:46:02 -04:00

test.display.js

Util shouldn't modify window object

2016-09-16 15:49:52 -04:00

test.helper.js

Move input-related files into core/input

2016-09-16 15:49:52 -04:00

test.keyboard.js

Move input-related files into core/input

2016-09-16 15:49:52 -04:00

test.rfb.js

Detect RealVNC's RFB 5.0 Protocol Version

2016-09-16 17:33:46 -04:00

test.util.js

Util shouldn't modify window object

2016-09-16 15:49:52 -04:00

test.websock.js

Fix failing test

2016-04-30 02:28:45 +02:00

vnc_perf.html

Move input-related files into core/input

2016-09-16 15:49:52 -04:00

vnc_playback.html

Move input-related files into core/input

2016-09-16 15:49:52 -04:00