ozone: Do not add display origin to bounds in pixels.

GetWindowBoundsInScreen adds display origin to
bounds in pixels, which is incorrect, because they contain
a location in screen, and adding additional offset results
in wrong positions for menus (when the browser is located
on a secondary display).

Bug: 927280
Change-Id: Ib16f46b095751cb3f29bfa6579d44eabdf104647
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497052Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#637604}

ui/views/widget/desktop_aura/desktop_window_tree_host_platform.cc

@@ -259,13 +259,7 @@ void DesktopWindowTreeHostPlatform::GetWindowPlacement(
 }
 
 gfx::Rect DesktopWindowTreeHostPlatform::GetWindowBoundsInScreen() const {
-  gfx::Rect bounds =
-      gfx::ConvertRectToDIP(device_scale_factor(), GetBoundsInPixels());
-  bounds += display::Screen::GetScreen()
-                ->GetDisplayNearestWindow(const_cast<aura::Window*>(window()))
-                .bounds()
-                .OffsetFromOrigin();
-  return bounds;
+  return gfx::ConvertRectToDIP(device_scale_factor(), GetBoundsInPixels());
 }
 
 gfx::Rect DesktopWindowTreeHostPlatform::GetClientAreaBoundsInScreen() const {