Factory reset screen is added

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

Index: chrome/browser/resources/chromeos/login/login.js
diff --git a/chrome/browser/resources/chromeos/login/login.js b/chrome/browser/resources/chromeos/login/login.js
index 439329ba279e30fdab318eff1d998cd1f8ba80fd..094c0576721f653ebc781d27444286ac1e627867 100644
--- a/chrome/browser/resources/chromeos/login/login.js
+++ b/chrome/browser/resources/chromeos/login/login.js
@@ -36,6 +36,7 @@ cr.define('cr.ui', function() {
     login.GaiaSigninScreen.register();
     oobe.OAuthEnrollmentScreen.register();
     oobe.UserImageScreen.register(/* lazyInit= */ true);
+    oobe.ResetScreen.register();

[Nikita (slow), 2012/09/12 13:22:21]

Please place into login.* namespace

[glotov, 2012/09/12 22:40:25]

It is still managed by WizardController. Just like oobe.OAuthEnrollmentScreen.

[Nikita (slow), 2012/09/13 07:35:59]

Ok, but my point was regarding logical definition of OOBE which is out of box
experience.
Technically enrollment belongs here. In some sense UserImageScreen belongs there
too as it is launched in context of OOBE but than as a context of new user signs
in.
Reset usually is launched as a part of normal login screen i.e. not part of
OOBE.

But let's leave it as is.

[glotov, 2012/09/14 16:37:02]

Done.

     login.ErrorMessageScreen.register();
 
     cr.ui.Bubble.decorate($('bubble'));