Don't relaunch app for non-auth errors.

remoting/webapp/crd/js/remoting.js

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 'use strict';
 
 /** @suppress {duplicate} */
 var remoting = remoting || {};
 
 /**
@@ skipping 164 matching lines @@
  * Chromoting again.
  *
  * @param {remoting.Error} error
  * @return {void} Nothing.
  */
 remoting.showErrorMessage = function(error) {
   l10n.localizeElementFromTag(
       document.getElementById('token-refresh-error-message'),
       error);
   var auth_failed = (error == remoting.Error.AUTHENTICATION_FAILED);
-  if (base.isAppsV2()) {

[kelvinp, 2015/03/04 21:06:56]

I think another problem is that at error.js

https://code.google.com/p/chromium/codesearch#chromium/src/remoting/webapp/cr...

We handle all unknown HTTP error as AUTHENTICATION_FAILED.
Would that needs to be addressed as well?

[Jamie, 2015/03/04 23:11:19]

Kelvin and I discussed in person, and felt that since unexpected HTTP response
codes are (hopefully) rare, we can ignore that problem for the time being.

+  if (auth_failed && base.isAppsV2()) {
     remoting.handleAuthFailureAndRelaunch();
   } else {
     document.getElementById('token-refresh-auth-failed').hidden = !auth_failed;
     document.getElementById('token-refresh-other-error').hidden = auth_failed;
     remoting.setMode(remoting.AppMode.TOKEN_REFRESH_FAILED);
   }
 };
 
 /**
  * Determine whether or not the app is running in a window.
@@ skipping 12 matching lines @@
     } else {
       chrome.windows.get(tab.windowId, null, windowCallback);
     }
   };
   if (chrome.tabs) {
     chrome.tabs.getCurrent(tabCallback);
   } else {
     console.error('chome.tabs is not available.');
   }
 }