Accessible bounds should include device scale factor on Windows (again)

content/browser/accessibility/browser_accessibility_win.cc

Index: content/browser/accessibility/browser_accessibility_win.cc
diff --git a/content/browser/accessibility/browser_accessibility_win.cc b/content/browser/accessibility/browser_accessibility_win.cc
index 01b5e28fd78e4782c85ca438de5f67de756504b0..caa2c6c39edc8378b9ca4a7a07c72ae69c8643f3 100644
--- a/content/browser/accessibility/browser_accessibility_win.cc
+++ b/content/browser/accessibility/browser_accessibility_win.cc
@@ -4274,22 +4274,6 @@ void BrowserAccessibilityWin::OnLocationChanged() {
   FireNativeEvent(EVENT_OBJECT_LOCATIONCHANGE);
 }
 
-gfx::Rect BrowserAccessibilityWin::RelativeToAbsoluteBounds(
-    gfx::RectF bounds,
-    bool frame_only) const {
-  gfx::Rect result =
-      BrowserAccessibility::RelativeToAbsoluteBounds(bounds, frame_only);
-
-  // On Windows, we have to divide by the device scale factor to get
-  // pixels in the coordinates that MSAA clients expect.
-  float device_scale_factor = manager()->device_scale_factor();
-  if (device_scale_factor > 0.0 && device_scale_factor != 1.0) {
-    result = ScaleToEnclosingRect(result, 1.0 / device_scale_factor,
-                                  1.0 / device_scale_factor);
-  }
-  return result;
-}
-
 std::vector<base::string16> BrowserAccessibilityWin::ComputeTextAttributes()
     const {
   std::vector<base::string16> attributes;