Create OOBE screen for Voice Interaction value proposition

chrome/browser/chromeos/first_run/first_run.cc

Index: chrome/browser/chromeos/first_run/first_run.cc
diff --git a/chrome/browser/chromeos/first_run/first_run.cc b/chrome/browser/chromeos/first_run/first_run.cc
index e4ea95643bcd74425a7bd6ed1faf816a4edc866c..5be34f3f4c6b42b1b26f376b34a54aa0df7a1195 100644
--- a/chrome/browser/chromeos/first_run/first_run.cc
+++ b/chrome/browser/chromeos/first_run/first_run.cc
@@ -45,6 +45,12 @@ void LaunchDialogForProfile(Profile* profile) {
   if (!extension)
     return;
 
+  // If voice interaction value prop has been accepted, the tutorial will be
+  // shown after the voice interaction OOBE flow.
+  if (profile->GetPrefs()->GetBoolean(
+          prefs::kArcVoiceInteractionValuePropAccepted))

[xiyuan, 2017/05/30 19:26:21]

How would this play along with MaybeLaunchDialogAfterSessionStart() and
MaybeLaunchDialogImmediately() ? I wonder whether we should do the skipping at
where those two calls are made instead of here.

[xc, 2017/05/31 18:37:52]

+1 We may have to show this more than once even if user accepted it, e.g. user
accepted the value prop but declined the UDC later. 

[yueli, 2017/06/02 02:03:46]

Done.

+    return;
+
   OpenApplication(AppLaunchParams(
       profile, extension, extensions::LAUNCH_CONTAINER_WINDOW,
       WindowOpenDisposition::NEW_WINDOW, extensions::SOURCE_CHROME_INTERNAL));