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

 // Copyright 2014 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.
 
 #include "chrome/browser/chromeos/login/supervised/supervised_user_login_flow.h"
 
 #include "base/base64.h"
 #include "base/logging.h"
 #include "base/metrics/histogram.h"
 #include "base/prefs/pref_registry_simple.h"
@@ skipping 29 matching lines @@
 }
 
 bool SupervisedUserLoginFlow::ShouldLaunchBrowser() {
   return data_loaded_;
 }
 
 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;
 }
 
 bool SupervisedUserLoginFlow::HandlePasswordChangeDetected() {
   return false;
 }
 
 void SupervisedUserLoginFlow::HandleOAuthTokenStatusChange(
     user_manager::User::OAuthTokenStatus status) {
@@ skipping 189 matching lines @@
 void SupervisedUserLoginFlow::LaunchExtraSteps(
     Profile* profile) {
   profile_ = profile;
   ChromeUserManager::Get()->GetSupervisedUserManager()->LoadSupervisedUserToken(
       profile,
       base::Bind(&SupervisedUserLoginFlow::OnSyncSetupDataLoaded,
                  weak_factory_.GetWeakPtr()));
 }
 
 }  // namespace chromeos