Put OOBE UI on touch display if no keyboard detected

chrome/browser/chromeos/login/ui/login_display_host_impl.cc

Index: chrome/browser/chromeos/login/ui/login_display_host_impl.cc
diff --git a/chrome/browser/chromeos/login/ui/login_display_host_impl.cc b/chrome/browser/chromeos/login/ui/login_display_host_impl.cc
index 6db2b1af8b0e70bb4d47adbe482ba8dd6dcb53d3..a1313079fa543137bcae70deb2b515f51b772143 100644
--- a/chrome/browser/chromeos/login/ui/login_display_host_impl.cc
+++ b/chrome/browser/chromeos/login/ui/login_display_host_impl.cc
@@ -975,6 +975,8 @@ void LoginDisplayHostImpl::OnActiveOutputNodeChanged() {
 // LoginDisplayHostImpl, display::DisplayObserver:
 
 void LoginDisplayHostImpl::OnDisplayAdded(const display::Display& new_display) {
+  if (GetOobeUI())
+    GetOobeUI()->OnDisplayAdded();
 }

[oshima, 2017/05/10 00:14:31]

I think you need to handle removed case. 

- You have one non touch + two touch displays
- Removing a touch display that is used as a primary will change
 the display configuration. It may or may not use the touch capable one.

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

Addressed in Patch set 3 by triggering a re-evaluation of the display usage on
display removal as well.

 
 void LoginDisplayHostImpl::OnDisplayRemoved(