Abstract RFB errors to avoid sending strings

The API allowed strings to be passed from the RFB module to the
application using the disconnect reason. This caused problems since
the application didn't have control over translations for these
strings.

Most of the information being passed using this string was very
technical and not helpful to the end user. One exception to this was
the security result information regarding for example authentication
failures. The protocol allows the VNC server to pass a string
directly to the user in the security result.

So the disconnect reason is replaced by a boolean saying if the
disconnection was clean or not. And for the security result information
from the server, a new event has been added.

1 files changed, 3 insertions, 3 deletions

diff --git a/vnc_lite.html b/vnc_lite.html
index b904b4a..762da01 100644
--- a/vnc_lite.html
+++ b/vnc_lite.html
@@ -162,10 +162,10 @@
         function disconnected(e) {
             document.getElementById('sendCtrlAltDelButton').disabled = true;
             updatePowerButtons();
-            if (typeof(e.detail.reason) !== 'undefined') {
-                status(e.detail.reason, "error");
-            } else {
+            if (e.detail.clean) {
                 status("Disconnected", "normal");
+            } else {
+                status("Something went wrong, connection is closed", "error");
             }
         }