Put OOBE UI on touch display if no keyboard detected

chrome/browser/ui/webui/chromeos/login/oobe_ui.h

Index: chrome/browser/ui/webui/chromeos/login/oobe_ui.h
diff --git a/chrome/browser/ui/webui/chromeos/login/oobe_ui.h b/chrome/browser/ui/webui/chromeos/login/oobe_ui.h
index 035cbbdc9bbc346dc46f5145ea48be3859f7d40a..c40509b2df9afe39e2742c0b6bd89bb7a96db602 100644
--- a/chrome/browser/ui/webui/chromeos/login/oobe_ui.h
+++ b/chrome/browser/ui/webui/chromeos/login/oobe_ui.h
@@ -53,6 +53,7 @@ class NativeWindowDelegate;
 class NetworkDropdownHandler;
 class NetworkStateInformer;
 class NetworkView;
+class OobeDisplayChooser;
 class SigninScreenHandler;
 class SigninScreenHandlerDelegate;
 class SupervisedUserCreationScreenHandler;
@@ -170,6 +171,9 @@ class OobeUI : public content::WebUIController,
   // changed).
   void UpdateLocalizedStringsIfNeeded();
 
+  // Re-evaluate OOBE display placement taking a new display into consideration.
+  void OnDisplayAdded();
+
  private:
   // Lookup a view by its statically registered OobeScreen.
   template <typename TView>
@@ -241,6 +245,8 @@ class OobeUI : public content::WebUIController,
 
   std::unique_ptr<ash::ScreenDimmer> screen_dimmer_;
 
+  std::unique_ptr<OobeDisplayChooser> oobe_display_chooser_;

[jdufault, 2017/05/09 18:59:38]

Consider using base::Optional, up to you.

+
   // Store the deferred JS calls before the screen handler instance is
   // initialized.
   std::unique_ptr<JSCallsContainer> js_calls_container;