Fix bug where accessibility could "see behind" infobars.

Fix bug where accessibility could "see behind" infobars.

This swallows all hover events that are unhandled by an infobar before
they reach the ContentView. This prevents a bug in accessibility mode
where if the user clicked on an empty space in the infobar then an
element from the webpage behind the infobar would be selected.

BUG=430701
Committed: https://crrev.com/1ea31ca6935e488fdbb116bf81316cec1e7453bf
Cr-Commit-Position: refs/heads/master@{#309454}

[newt (away), 2014-12-22 18:28:15]

newt@chromium.org changed reviewers:
+ dmazzoni@chromium.org

[newt (away), 2014-12-22 18:28:15]

PTAL

[dmazzoni, 2014-12-22 19:10:48]

lgtm

https://codereview.chromium.org/824763002/diff/1/chrome/android/java/src/org/...
File
chrome/android/java/src/org/chromium/chrome/browser/infobar/InfoBarContainer.java
(right):

https://codereview.chromium.org/824763002/diff/1/chrome/android/java/src/org/...
chrome/android/java/src/org/chromium/chrome/browser/infobar/InfoBarContainer.java:198:
// Consume all hover events so they do not reach the ContentView. In
accessibility mode,
Nit: "touch exploration" mode or "touch exploration mode for accessibility" or
something like that, because technically the user can choose to enable
accessibility but not enable touch exploration - for example if they're using a
keyboard only, or using accessibility apis for automation

[newt (away), 2014-12-22 19:14:24]

https://codereview.chromium.org/824763002/diff/1/chrome/android/java/src/org/...
File
chrome/android/java/src/org/chromium/chrome/browser/infobar/InfoBarContainer.java
(right):

https://codereview.chromium.org/824763002/diff/1/chrome/android/java/src/org/...
chrome/android/java/src/org/chromium/chrome/browser/infobar/InfoBarContainer.java:198:
// Consume all hover events so they do not reach the ContentView. In
accessibility mode,
On 2014/12/22 19:10:47, dmazzoni wrote:
> Nit: "touch exploration" mode or "touch exploration mode for accessibility" or
> something like that, because technically the user can choose to enable
> accessibility but not enable touch exploration - for example if they're using
a
> keyboard only, or using accessibility apis for automation

Done.

[newt (away), 2014-12-22 19:14:28]

The CQ bit was checked by newt@chromium.org

[commit-bot: I haz the power, 2014-12-22 19:14:56]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/824763002/20001

[commit-bot: I haz the power, 2014-12-22 20:28:11]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-12-22 20:30:38]

Patchset 2 (id:??) landed as
https://crrev.com/1ea31ca6935e488fdbb116bf81316cec1e7453bf
Cr-Commit-Position: refs/heads/master@{#309454}

[aurimas (slooooooooow), 2015-01-29 02:38:19]

aurimas@chromium.org changed reviewers:
+ aurimas@chromium.org

[aurimas (slooooooooow), 2015-01-29 02:38:19]

lgtm