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

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.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=95808

[Mattias Nissler (ping if slow), 2011-08-05 22:29:07]

Actually, here is another CL that I forgot to upload earlier.

[James Hawkins, 2011-08-05 22:36:19]

LGTM with nit.

http://codereview.chromium.org/7550048/diff/1/chrome/browser/resources/chrome...
File chrome/browser/resources/chromeos/login/oobe_screen_enrollment.js (right):

http://codereview.chromium.org/7550048/diff/1/chrome/browser/resources/chrome...
chrome/browser/resources/chromeos/login/oobe_screen_enrollment.js:41: * @param
data {object} Screen init payload.
@param {object} data

[whywhat, 2011-08-08 08:11:14]

LGTM

[Mattias Nissler (ping if slow), 2011-08-08 11:29:08]

http://codereview.chromium.org/7550048/diff/1/chrome/browser/resources/chrome...
File chrome/browser/resources/chromeos/login/oobe_screen_enrollment.js (right):

http://codereview.chromium.org/7550048/diff/1/chrome/browser/resources/chrome...
chrome/browser/resources/chromeos/login/oobe_screen_enrollment.js:41: * @param
data {object} Screen init payload.
On 2011/08/05 22:36:19, James Hawkins wrote:
> @param {object} data

Done.