[cros] OOBE: add histograms for Profile image fetching.

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

 // Copyright (c) 2011 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.
 
 /**
  * @fileoverview Oobe user image screen implementation.
  */
 
 cr.define('oobe', function() {
 
@@ skipping 193 matching lines @@
         this.acceptImage_();
     },
 
     /**
      * Event handler that is invoked just before the screen is shown.
      * @param {object} data Screen init payload.
      */
     onBeforeShow: function(data) {
       Oobe.getInstance().headerHidden = true;
       $('user-image-grid').updateAndFocus();
+      chrome.send('onUserImageScreenShown', [(new Date()).getTime()/1000]);

[zel, 2011/10/20 21:57:44]

you should not use time from JS side here, you should get current time on C++
side when this even arrives.

[Ivan Korotkov, 2011/10/21 07:52:00]

Why? I'm interested in the delay between Show() is called in C++ code and the
Oobe.showScreen call is made (this delay is caused by an amount of extensions
being synced at the same time, etc).

[Ivan Korotkov, 2011/10/21 12:29:52]

Hm, ok, as discussed offline it's better to use a consistent clock source, so
moving this to C++ side.

     },
 
     /**
      * Accepts currently selected image, if possible.
      * @private
      */
     acceptImage_: function() {
       if (!$('ok-button').disabled)
         chrome.send('onUserImageAccepted');
     },
@@ skipping 100 matching lines @@
   ].forEach(function(name) {
     UserImageScreen[name] = function(value) {
       $('user-image')[name + '_'](value);
     };
   });
 
   return {
     UserImageScreen: UserImageScreen
   };
 });