CrOS OOBE: Load gaia login frame only after dialogArguments have been initialized.

If the gaia login frame is loaded right away when the main OOBE UI loads, there's no chance for the enrollment handler to set up chrome.dialogArguments, which gaia_login.js however requires to initialize correctly. So, defer loading of the gaia login frame to the point the enterprise enrollment screen actually gets shown.

BUG=chromium-os:18736
TEST=Enrollment triggered through the accelerator finally works.

Review URL: http://codereview.chromium.org/7550048

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95808 0039d316-1c4b-4281-b951-d872f2087c98

chrome/browser/resources/chromeos/login/oobe_screen_enrollment.html

@@ -26,8 +26,7 @@
       </div>
     </div>
     <div id="enroll-login-form">
-      <iframe id="gaia-local-login" scrolling="no"
-          src="chrome://oobe/gaialogin"></iframe>
+      <iframe id="gaia-local-login" scrolling="no"></iframe>
     </div>
   </div>
   <div id="enroll-confirmation-screen" hidden>

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

@@ -36,6 +36,15 @@ cr.define('oobe', function() {
       return localStrings.getString('loginHeader');
     },
 
+    /**
+     * Event handler that is invoked just before the frame is shown.
+     * @param {object} data Screen init payload.
+     */
+    onBeforeShow: function(data) {
+      // Reload the gaia frame.
+      $('gaia-local-login').src = 'chrome://oobe/gaialogin';
+    },
+
     /**
      * Buttons in oobe wizard's button strip.
      * @type {array} Array of Buttons.