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

commit 4089977fdebad10fac160d2a43d65b97f00d92ab
Author: nektar <nektar@chromium.org>
Date: Fri Mar 17 02:49:39 2017

WIP: Modified AXPosition to work with objects with both embedded object characters and text.

On Windows, I had assumed that we would use tree positions for non text nobjects and text positions for text objects. This can work only if IA2 hypertext contains either a series of embedded object characters or text, but not both.
However, the fact that we append the text of each static text object to its immediate parent for performance reasons, means that we could potentially have IA2 hypertext that contains both embedded object characters and text.
BUG=700214
R=dmazzoni@chromium.org
TESTED=not yet

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

[modify] https://crrev.com/4089977fdebad10fac160d2a43d65b97f00d92ab/content/browser/accessibility/ax_platform_position.cc
[modify] https://crrev.com/4089977fdebad10fac160d2a43d65b97f00d92ab/content/browser/accessibility/ax_platform_position.h
[modify] https://crrev.com/4089977fdebad10fac160d2a43d65b97f00d92ab/ui/accessibility/ax_node.cc
[modify] https://crrev.com/4089977fdebad10fac160d2a43d65b97f00d92ab/ui/accessibility/ax_node.h
[modify] https://crrev.com/4089977fdebad10fac160d2a43d65b97f00d92ab/ui/accessibility/ax_position.h

Nektarios, is the status of started still correct here? 

Changing priority since this is concerning text navigation.