Updated KioskAppManager to track whether an app was auto-launched.

chrome/browser/chromeos/login/ui/login_display_host.h

Index: chrome/browser/chromeos/login/ui/login_display_host.h
diff --git a/chrome/browser/chromeos/login/ui/login_display_host.h b/chrome/browser/chromeos/login/ui/login_display_host.h
index 18032e673078777977724ab1a4299d6f83c1eda8..9d4821b0836b9b4e099724be8831fd1a127238b2 100644
--- a/chrome/browser/chromeos/login/ui/login_display_host.h
+++ b/chrome/browser/chromeos/login/ui/login_display_host.h
@@ -89,9 +89,11 @@ class LoginDisplayHost {
   // Initiates authentication network prewarming.
   virtual void PrewarmAuthentication() = 0;
 
-  // Starts app launch splash screen.
+  // Starts app launch splash screen. If |is_auto_launch| is true, the app is
+  // being auto-launched on startup.

[bartfab (slow), 2015/02/06 12:07:39]

Nit: "on startup" is somewhat ambiguous. It sounds synonymous to "on boot" to me
but this is not actually what happens. The auto-launch code is triggered
whenever we reach the login screen, whether on boot, on logout or on crash.

[Andrew T Wilson (Slow), 2015/02/06 13:24:21]

Done.

   virtual void StartAppLaunch(const std::string& app_id,
-                              bool diagnostic_mode) = 0;
+                              bool diagnostic_mode,
+                              bool is_auto_launch) = 0;
 
   // Starts the demo app launch.
   virtual void StartDemoAppLaunch() = 0;