Inline sign in extracts gaia id from HTTP header and seeds account tracker

chrome/browser/resources/chromeos/login/login_common.js

Index: chrome/browser/resources/chromeos/login/login_common.js
diff --git a/chrome/browser/resources/chromeos/login/login_common.js b/chrome/browser/resources/chromeos/login/login_common.js
index 3dc3b63e08bbcfbee1c534728c2010b4ae715fa6..34c6e5e912f949729d3ba507aeb5a46996bf4c49 100644
--- a/chrome/browser/resources/chromeos/login/login_common.js
+++ b/chrome/browser/resources/chromeos/login/login_common.js
@@ -262,7 +262,8 @@ cr.define('cr.ui', function() {
   Oobe.loginForTesting = function(username, password) {
     Oobe.disableSigninUI();
     chrome.send('skipToLoginForTesting', [username]);
-    chrome.send('completeLogin', [username, password, false]);
+    // TODO(rogerta): expose gaiaId to caller?

[achuithb, 2014/10/21 21:11:00]

Is there a bug-id that you could reference here? I don't think this TODO is
necessary since this is a 'fake' login.

What are the ramifications of gaiaId?

[Roger Tawa OOO till Jul 10th, 2014/10/21 21:35:25]

This was more of a question than a bug.  I will remove the comment.  The gaiaid
is a number that uniquely identifies a gaia account.  The email is not good
enough because it can change over time, and some characters like "." are not
significant.

+    chrome.send('completeLogin', ['fake-gaia-id', username, password, false]);

[achuithb, 2014/10/21 21:11:00]

Is this going to work? I hope this won't break telemetry on chromeos.

[Roger Tawa OOO till Jul 10th, 2014/10/21 21:35:25]

Oops, should be a numeric field.  Done.

   };
 
   /**