Merge to M53: Don't post events on internal nodes in the accessibility tree on Android.

Merge to M53: Don't post events on internal nodes in the accessibility tree on Android.

Sometimes we get events on nodes in the internal accessibility tree that
are not exposed on that platform or under all circumstances. On Android
that led to an issue where after closing a SELECT pop-up, we got a focus
event on the OPTION and subsequent navigation was trapped inside that
control rather than outside it.

The fix is to map the focus event to the topmost leaf ancestor, which
in this case would be the SELECT element.

BUG=652805
Review-Url: https://codereview.chromium.org/2397503002
Cr-Commit-Position: refs/heads/master@{#422944}
(cherry picked from commit 7969d3a5bcf2af3fac57c3acef518298e8c48382)

Committed: https://chromium.googlesource.com/chromium/src/+/1b6eb6de84f9ccf47005fb59351de98b0719a877

[dmazzoni, 2016-10-10 18:41:02]

Description was changed from

==========
Merge to M53: Don't post events on internal nodes in the accessibility tree on
Android.

Sometimes we get events on nodes in the internal accessibility tree that
are not exposed on that platform or under all circumstances. On Android
that led to an issue where after closing a SELECT pop-up, we got a focus
event on the OPTION and subsequent navigation was trapped inside that
control rather than outside it.

The fix is to map the focus event to the topmost leaf ancestor, which
in this case would be the SELECT element.

BUG=652805

Review-Url: https://codereview.chromium.org/2397503002
Cr-Commit-Position: refs/heads/master@{#422944}
(cherry picked from commit 7969d3a5bcf2af3fac57c3acef518298e8c48382)
==========

to

==========
Merge to M53: Don't post events on internal nodes in the accessibility tree on
Android.

Sometimes we get events on nodes in the internal accessibility tree that
are not exposed on that platform or under all circumstances. On Android
that led to an issue where after closing a SELECT pop-up, we got a focus
event on the OPTION and subsequent navigation was trapped inside that
control rather than outside it.

The fix is to map the focus event to the topmost leaf ancestor, which
in this case would be the SELECT element.

BUG=652805

Review-Url: https://codereview.chromium.org/2397503002
Cr-Commit-Position: refs/heads/master@{#422944}
(cherry picked from commit 7969d3a5bcf2af3fac57c3acef518298e8c48382)

Committed:
https://chromium.googlesource.com/chromium/src/+/1b6eb6de84f9ccf47005fb59351d...
==========

[dmazzoni, 2016-10-10 18:41:03]

Committed patchset #1 (id:1) manually as
1b6eb6de84f9ccf47005fb59351de98b0719a877.