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

remoting/webapp/crd/js/desktop_remoting.js

Index: remoting/webapp/crd/js/desktop_remoting.js
diff --git a/remoting/webapp/crd/js/desktop_remoting.js b/remoting/webapp/crd/js/desktop_remoting.js
index ab266268e261f9d811f05e1704148798f87e477a..7f3fc59dc40f45216ed1ead49df327c595c27f6d 100644
--- a/remoting/webapp/crd/js/desktop_remoting.js
+++ b/remoting/webapp/crd/js/desktop_remoting.js
@@ -69,10 +69,21 @@ remoting.DesktopRemoting.prototype.init = function() {
   remoting.initGlobalEventHandlers();
 
   if (base.isAppsV2()) {
-    remoting.fullscreen = new remoting.FullscreenAppsV2();
     remoting.windowFrame = new remoting.WindowFrame(
         document.getElementById('title-bar'));
     remoting.optionsMenu = remoting.windowFrame.createOptionsMenu();
+
+    remoting.fullscreen = new remoting.FullscreenAppsV2();

[Jamie, 2015/01/23 22:37:24]

Moving this here feels cleaner because it allows the code that uses
remoting.fullscreen to be placed immediately after its creation, rather than
relying on the fact that initGlobalObjects creates it.

+    remoting.fullscreen.addListener(function(isFullscreen) {
+      chrome.storage.local.set({'start-fullscreen': isFullscreen});
+    });
+    // When a window goes full-screen, a resize event is triggered, but the
+    // Fullscreen.isActive call is not guaranteed to return true until the
+    // full-screen event is triggered. In apps v2, the size of the window's
+    // client area is calculated differently in full-screen mode, so register
+    // for both events.
+    remoting.fullscreen.addListener(remoting.onResize);
+
   } else {
     remoting.fullscreen = new remoting.FullscreenAppsV1();
     remoting.toolbar = new remoting.Toolbar(