Don't allow restarting to apply custom flags when supervised user creation flow is active

chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc

Index: chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
diff --git a/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc b/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
index 0f9a84eab4a7524d8146f30617d9e8bdc2da4f58..890b3fd7e20eac7e8eb77d62a5396b0991370b5c 100644
--- a/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
+++ b/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
@@ -47,6 +47,10 @@ bool SupervisedUserLoginFlow::ShouldSkipPostLoginScreens() {
   return true;
 }
 
+bool SupervisedUserLoginFlow::SupportsEarlyRestartToApplyFlags() {
+  return true;

[Nikita (slow), 2014/10/15 18:12:48]

Supervised user login is actually guarded here:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chr...

Not sure why supervised users are not allowed to set custom flags.
I guess if we allow restart to apply flags, we'll use this call:

SupervisedUserLoginFlow::LaunchExtraSteps()

Do you agree that we should return false here too?

[Nikita (slow), 2014/10/16 09:45:06]

I've changed this to false in second patchset.

+}
+
 bool SupervisedUserLoginFlow::HandleLoginFailure(const AuthFailure& failure) {
   return false;
 }