Fix SHIFT+TAB order on GAIA login screens

chrome/browser/resources/gaia_auth_host/authenticator.js

Index: chrome/browser/resources/gaia_auth_host/authenticator.js
diff --git a/chrome/browser/resources/gaia_auth_host/authenticator.js b/chrome/browser/resources/gaia_auth_host/authenticator.js
index c5a1da21c949682e3785a6a25cde77f4c79d2104..ccee2cec1158b94da9a671ad34f66e4252e3b62e 100644
--- a/chrome/browser/resources/gaia_auth_host/authenticator.js
+++ b/chrome/browser/resources/gaia_auth_host/authenticator.js
@@ -322,7 +322,8 @@ cr.define('cr.login', function() {
    * @private
    */
   Authenticator.prototype.onFocus_ = function(e) {
-    this.webview_.focus();
+    if (!this.isNewGaiaFlowChromeOS)

[xiyuan, 2015/06/10 17:43:03]

It is probably more correct to check (authMode == AuthMode.DESKTOP). 
How about remember authMode in Authenticator.prototype.load and test it here?

The worry is that we might switch to new gaia flow in ChromeOS mirror later and
would run it in a tab as well. And isNewGaiaFlowChromeOS might not tell the
difference.

[Greg Levin, 2015/06/10 20:01:25]

Done.

+      this.webview_.focus();
   };
 
   /**