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..c0e92ef9e1ba1d282120e32b73333524ca263675 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,8 @@ class OobeUI : public content::WebUIController,
   // changed).
   void UpdateLocalizedStringsIfNeeded();
 
+  void OnDisplayAdded(const display::Display& new_display);

[jdufault, 2017/05/08 17:44:58]

Add comment.

[jdufault, 2017/05/08 17:44:58]

|new_display| is unused, remove it. Is OnDisplayConfigurationChanged a better
name? What happens when we remove a display?

[Felix Ekblom, 2017/05/09 08:54:50]

I've assumed only one touch display for the initial work on this task to
simplify as much as possible. Reacting to OnDisplayRemoved() could be
interesting for a follow up CL, as well as using a better display choosing
heuristic, if we assume multiple connected touch displays. 

[Felix Ekblom, 2017/05/10 10:59:13]

I renamed the method according to your suggestion as a part of Patch set 3.

+
  private:
   // Lookup a view by its statically registered OobeScreen.
   template <typename TView>
@@ -241,6 +244,8 @@ class OobeUI : public content::WebUIController,
 
   std::unique_ptr<ash::ScreenDimmer> screen_dimmer_;
 
+  std::unique_ptr<OobeDisplayChooser> oobe_display_chooser_;
+
   // Store the deferred JS calls before the screen handler instance is
   // initialized.
   std::unique_ptr<JSCallsContainer> js_calls_container;