Work around bad line break offset calculation

Work around bad line break offset calculation

Line breaks, as computed by AXNode, are wrong. One instance is the very last start offset it pushes. Since there's no way for the computation to know whether the last node on a line actually results in a *text* line break (i.e. a line break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break offset.

BUG=652059
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

[David Tseng, 2016-10-06 21:23:08]

Description was changed from

==========
Work around bad line break offset calcuation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=
==========

to

==========
Work around bad line break offset calcuation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-10-06 21:25:03]

Description was changed from

==========
Work around bad line break offset calcuation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Work around bad line break offset calcuation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=652059
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-10-06 21:25:03]

dtseng@chromium.org changed reviewers:
+ nektar@chromium.org

[David Tseng, 2016-10-07 19:43:08]

Description was changed from

==========
Work around bad line break offset calcuation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=652059
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Work around bad line break offset calculation

Line breaks, as computed by AXNode, are wrong. One instance is the very last
start offset it pushes. Since there's no way for the computation to know whether
the last node on a line actually results in a *text* line break (i.e. a line
break represented in the selection), it's unreliable and causes problems.

For now, work around it in ChromeVox by just ignoring the last line break
offset.

BUG=652059
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[nektarios, 2016-10-07 21:37:34]

lgtm