Moves FindDisplayIndexContainingPoint into display

ui/display/display_finder.h

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef UI_DISPLAY_DISPLAY_FINDER_H_
 #define UI_DISPLAY_DISPLAY_FINDER_H_
 
 #include <vector>
 
 #include "ui/display/display_export.h"
 
 namespace gfx {
 class Point;
 class Rect;
 }
 
 namespace display {
 class Display;
 
-// Returns the display in |displays| closest to |point|.
+// Returns the display containing |point|. If no displays contain |point|, then
+// this returns the display closest to |point|.
 DISPLAY_EXPORT const Display* FindDisplayNearestPoint(
     const std::vector<Display>& displays,
     const gfx::Point& point);
 
 // Returns the display in |displays| with the biggest intersection of |rect|.
 // If none of the displays intersect |rect| null is returned.
 DISPLAY_EXPORT const Display* FindDisplayWithBiggestIntersection(
     const std::vector<Display>& displays,
     const gfx::Rect& rect);
 
+// Returns the index in |displays| whose bounds contains |point_in_screen|.
+// Returns -1 if no such Display contains |point_in_screen|.
+DISPLAY_EXPORT int FindDisplayIndexContainingPoint(

[kylechar, 2017/03/06 18:00:20]

Would it be "more" correct to return an iterator into |displays| here? Not that
there would ever be more more than INT_MAX displays in reality .

[sky, 2017/03/06 18:22:00]

I just copy/pasted the code. But I agree, an iterator makes more sense here.
Updated.

+    const std::vector<Display>& displays,
+    const gfx::Point& point_in_screen);
+
 }  // namespace display
 
 #endif  // UI_DISPLAY_DISPLAY_FINDER_H_