The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7

commit 78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7
Author: nektar <nektar@chromium.org>
Date: Wed Apr 27 08:13:45 2016

Correctly finds line boundaries in objects with rich text on Windows.

The issue is that we were not taking into account embedded object characters.
Took the opportunity to update the code to use the new |nextOnLine| and |previousOnLine| Blink APIs.
BUG= 605670 
R=dmazzoni@chromium.org

Review URL: https://codereview.chromium.org/1905263002

Cr-Commit-Position: refs/heads/master@{#390017}

[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/browser/accessibility/accessibility_win_browsertest.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/browser/accessibility/browser_accessibility.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/browser/accessibility/browser_accessibility.h
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/browser/accessibility/browser_accessibility_win.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/browser/accessibility/browser_accessibility_win_unittest.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/content/renderer/accessibility/blink_ax_tree_source.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/third_party/WebKit/LayoutTests/accessibility/inline-text-box-next-on-line.html
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.h
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/ui/accessibility/ax_enums.idl
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/ui/accessibility/ax_node_data.cc
[modify] https://crrev.com/78d5c7d32a7bd67f292397ddf7e79e079ff6f1d7/ui/accessibility/ax_tree_combiner.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5f4c668a1c89d82ba0fed9cc8912308b69e068f1

commit 5f4c668a1c89d82ba0fed9cc8912308b69e068f1
Author: nektar <nektar@chromium.org>
Date: Sat Apr 30 01:07:56 2016

Removes the restriction placed on the role of the accessibility object when calling the next/previousOnLine Blink APIs.

R=dmazzoni@chromium.org
BUG= 605670 

Review-Url: https://codereview.chromium.org/1941463002
Cr-Commit-Position: refs/heads/master@{#390827}

[modify] https://crrev.com/5f4c668a1c89d82ba0fed9cc8912308b69e068f1/content/browser/accessibility/browser_accessibility.cc
[modify] https://crrev.com/5f4c668a1c89d82ba0fed9cc8912308b69e068f1/content/renderer/accessibility/blink_ax_tree_source.cc
[modify] https://crrev.com/5f4c668a1c89d82ba0fed9cc8912308b69e068f1/third_party/WebKit/LayoutTests/accessibility/inline-text-box-next-on-line.html

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/74bdbcb2a0b6cd2810e8b666cd5fefbd600039fd

commit 74bdbcb2a0b6cd2810e8b666cd5fefbd600039fd
Author: nektar <nektar@chromium.org>
Date: Mon May 09 21:12:24 2016

The bug fixed involves not recursing into inline text boxes in the case that a static text object covered more than one line.

Also fixed a bug on Windows that didn't return the correct line boundaries if the start offset was equal to the text's length, something that is allowed by the IA2 Spec.
BUG= 605670 
R=dmazzoni@chromium.org
TESTED=manual testing with Gmail > Compose and Docs, browser tests

Review-Url: https://codereview.chromium.org/1951353002
Cr-Commit-Position: refs/heads/master@{#392424}

[modify] https://crrev.com/74bdbcb2a0b6cd2810e8b666cd5fefbd600039fd/content/browser/accessibility/accessibility_win_browsertest.cc
[modify] https://crrev.com/74bdbcb2a0b6cd2810e8b666cd5fefbd600039fd/content/browser/accessibility/browser_accessibility.cc
[modify] https://crrev.com/74bdbcb2a0b6cd2810e8b666cd5fefbd600039fd/content/browser/accessibility/browser_accessibility_win.cc