Allow full-screen mode when not connected, and remember the previous setting.

remoting/webapp/crd/js/client_session.js

Index: remoting/webapp/crd/js/client_session.js
diff --git a/remoting/webapp/crd/js/client_session.js b/remoting/webapp/crd/js/client_session.js
index 8c54cb743eedce5e197e53a30c940b372b61cf1a..17cb920f038aa9dcb8ec558fb200ef663fb339d5 100644
--- a/remoting/webapp/crd/js/client_session.js
+++ b/remoting/webapp/crd/js/client_session.js
@@ -611,13 +611,8 @@ remoting.ClientSession.prototype.removePlugin = function() {
     this.plugin_ = null;
   }
 
-  // Leave full-screen mode, and stop listening for related events.
-  var listener = this.callOnFullScreenChanged_;
-  remoting.fullscreen.activate(
-      false,
-      function() {
-        remoting.fullscreen.removeListener(listener);
-      });
+  // Stop listening for full-screen events.
+  remoting.fullscreen.removeListener(this.callOnFullScreenChanged_);

[kelvinp, 2015/01/23 23:39:58]

Rant: It is weird that sometimes the clientSession hooks its own fullscreen
listener like here, but sometimes via a proxy remoting.onResize().
IMHO, if clientSession needs to be shared among LG (which does't care about
fullscreen)  and chromoting.  It will be better to have the owning object of
client session to handle the event hooking.

[Jamie, 2015/01/24 00:46:35]

We are going to have to disentangle full-screen from this class, but we only
need it for bump-scroll support (which is also not used for app-remoting), so I
think we'll move both together in some clever way that Gary will come up with :)

   this.updateClientSessionUi_(null);
 
   this.container_.removeEventListener('mousemove',