Accessible bounds should include device scale factor on Windows.

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 dddc9c6b0be48a50293f1009504aba162a502de8..eead3d8efe990956e46025be7ba8fcbbccf091fb 100644
--- a/content/browser/accessibility/browser_accessibility_win.cc
+++ b/content/browser/accessibility/browser_accessibility_win.cc
@@ -4252,6 +4252,22 @@ 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;