Remove confusing keyboard test & focus on input device

chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc

Index: chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc
diff --git a/chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc b/chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc
index c15ebeaea036c60b6d6e1325240edd6758194913..ed115deb521fd728cfe527d45e5377611c8053e6 100644
--- a/chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc
+++ b/chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.cc
@@ -4,13 +4,18 @@
 
 #include "chrome/browser/ui/webui/chromeos/login/oobe_display_chooser.h"
 
+#include <stdint.h>
+#include <algorithm>

[oshima, 2017/07/07 14:22:10]

is this necessary?

[Felix Ekblom, 2017/07/07 19:04:30]

Removed.

+
 #include "ash/display/window_tree_host_manager.h"
 #include "ash/shell.h"
+#include "base/stl_util.h"
 #include "content/public/browser/browser_thread.h"
 #include "ui/display/display.h"
-#include "ui/display/display_layout.h"
 #include "ui/display/manager/display_manager.h"
 #include "ui/display/screen.h"
+#include "ui/events/devices/device_data_manager.h"
+#include "ui/events/devices/touchscreen_device.h"
 
 using content::BrowserThread;
 
@@ -23,6 +28,9 @@ bool TouchSupportAvailable(const display::Display& display) {
          display::Display::TouchSupport::TOUCH_SUPPORT_AVAILABLE;
 }
 
+// TODO(felixe): More context at crbug.com/738885
+const uint16_t kDeviceIds[] = {0x0457, 0x266e};
+
 }  // namespace
 
 OobeDisplayChooser::OobeDisplayChooser() : weak_ptr_factory_(this) {}
@@ -51,18 +59,24 @@ void OobeDisplayChooser::TryToPlaceUiOnTouchDisplay() {
 void OobeDisplayChooser::MoveToTouchDisplay() {
   DCHECK_CURRENTLY_ON(BrowserThread::UI);
 
-  const display::Displays& displays =
-      ash::Shell::Get()->display_manager()->active_only_display_list();
-
-  if (displays.size() <= 1)
+  if (!ui::DeviceDataManager::HasInstance())

[oshima, 2017/07/06 20:53:36]

can this happen?

[Felix Ekblom, 2017/07/07 08:41:01]

In theory, yes, since GetInstance() does not create the instance. In practice, I
don't think so but I don't know for sure.

Are you suggesting it should be safe to remove it?

[oshima, 2017/07/07 14:22:10]

If it should not happen, then remove check and fix if it happens.
Handling erroneous condition isn't recommended because it'll eventually leads to
wrong behavior anyway.

You may add DCHECK(device_manager) below to help diagnose if you want to
troubleshoot such case in bots, or local build.

[Felix Ekblom, 2017/07/07 19:04:30]

Very good point. Done.

     return;
 
-  for (const display::Display& display : displays) {
-    if (TouchSupportAvailable(display)) {
-      ash::Shell::Get()->window_tree_host_manager()->SetPrimaryDisplayId(
-          display.id());
-      break;
-    }
+  const ui::DeviceDataManager* device_manager =
+      ui::DeviceDataManager::GetInstance();
+  for (const ui::TouchscreenDevice& device :
+       device_manager->GetTouchscreenDevices()) {
+    if (!base::ContainsValue(kDeviceIds, device.vendor_id))
+      continue;
+
+    int64_t display_id =
+        device_manager->GetTargetDisplayForTouchDevice(device.id);
+    if (display_id == display::kInvalidDisplayId)
+      continue;
+
+    ash::Shell::Get()->window_tree_host_manager()->SetPrimaryDisplayId(
+        display_id);
+    break;
   }
 }