Start ARC and sign in after Chrome OS login

chromeos/chromeos_switches.cc

Index: chromeos/chromeos_switches.cc
diff --git a/chromeos/chromeos_switches.cc b/chromeos/chromeos_switches.cc
index 99860c7c379d531ffc9777609218a7e30b3c574e..6ba777667d32685912c9d077e297256c8902f59e 100644
--- a/chromeos/chromeos_switches.cc
+++ b/chromeos/chromeos_switches.cc
@@ -55,6 +55,12 @@ const char kAllowFailedPolicyFetchForTest[] =
 // mode. This can be enabled by this flag.
 const char kAllowRAInDevMode[] = "allow-ra-in-dev-mode";
 
+// Always starts ARC after login screen without Play Store, not only for primary

[Luis Héctor Chávez, 2017/02/27 17:13:15]

nit: we can make the wording stronger: "Always starts ARC after login screen
without Play Store. This still requires that both the hardware and
account/profile supports starting ARC." that way we tie it to normal ARC support
and don't have to update the wording every time we add support for more modes
(like AD auth).

[victorhsieh, 2017/02/28 18:57:33]

Actually, ARC will run without account/profile.  We will only have exception
case when ARC won't run, possibly including secondary profile.  Let me reword.

+// account, but also in most of the session such as Kiosk mode and guest mode.
+// Node that secondary account won't be supported. Play Store opt-in is still
+// required for user's account.
+const char kAlwaysStartArc[] = "always-start-arc";

[Luis Héctor Chávez, 2017/02/27 17:13:15]

for consistency with all the other ARC flags, can this be "arc-start-always"?
(even other non-ARC flags also seem to follow the convention of
kComponentFlag... or kDisableComponentFlag...)

[victorhsieh, 2017/02/28 18:57:33]

Done.  Also renamed the functions accordingly.

+
 // Specifies whether an app launched in kiosk mode was auto launched with zero
 // delay. Used in order to properly restore auto-launched state during session
 // restore flow.