Switched to using |AXPosition| for calculating word and line boundaries on Windows.

content/browser/accessibility/ax_platform_position.cc

Index: content/browser/accessibility/ax_platform_position.cc
diff --git a/content/browser/accessibility/ax_platform_position.cc b/content/browser/accessibility/ax_platform_position.cc
index 34d313929c307f958c8924b515d8eccc9621f36b..a41ed050051ba1adb2b74aaf7b5e3d19a437af05 100644
--- a/content/browser/accessibility/ax_platform_position.cc
+++ b/content/browser/accessibility/ax_platform_position.cc
@@ -109,6 +109,10 @@ int AXPlatformPosition::MaxTextOffsetInParent() const {
     return INVALID_OFFSET;
   if (GetAnchor()->IsTextOnlyObject())
     return MaxTextOffset();
+  // Objects in the shadow DOM are not visible to platform APIs and thus should

[dmazzoni, 2017/04/10 22:39:49]

Shadow DOM isn't necessarily the correct term here. Sometimes that's indeed
what's going on, for example if this is a <textarea> then the inner content is
the shadow DOM. But if it's just a static text object that's a leaf then the
inline text box is not really shadow DOM.

How about just saying something about: not all nodes in the internal
accessibility
tree are exposed to the platform.

+  // be excluded.
+  if (GetAnchor()->PlatformIsChildOfLeaf())
+    return MaxTextOffset();
   return 1;
 #else
   return MaxTextOffset();