Samuel Mannehed 67cd2072ab Allow specifying details when calling RFB._fail() ...

RFB's _fail function logs the error, disconnects the session and sets
disconnect_reason. The disconnect_reason is upon disconnection sent to
the user interface. It is thus not suitable for including error details
that aren't user friendly. The idea is that you will look in the
browser console for a full log with details of the error.

2016-11-10 15:17:37 +01: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

New way of detecting touch

2016-10-14 02:41:06 +02:00

playback.js

Support older base64 recordings

2016-10-05 10:20:17 +02: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

Wait for proper image load event

2016-10-24 14:42:13 +02:00

test.helper.js

Comment out skipped test

2016-11-10 14:28:40 +01:00

test.keyboard.js

Move input-related files into core/input

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

test.rfb.js

Allow specifying details when calling RFB._fail()

2016-11-10 15:17:37 +01: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

Support older base64 recordings

2016-10-05 10:20:17 +02:00

vnc_playback.html

Support older base64 recordings

2016-10-05 10:20:17 +02:00