diff options
| author | dmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-24 17:56:03 +0000 |
|---|---|---|
| committer | dmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-24 17:56:03 +0000 |
| commit | 8b494dad6d8e92f188fb60af2db7f8277dd3974a (patch) | |
| tree | 9e1e29fd4b810349d2a3fdf8b58d4c85d4e1c5a2 /ui/base/README.chromium | |
| parent | b0fde2ba0c664e85f9cb0c81330d1389cead9b40 (diff) | |
| download | chromium_src-8b494dad6d8e92f188fb60af2db7f8277dd3974a.zip chromium_src-8b494dad6d8e92f188fb60af2db7f8277dd3974a.tar.gz chromium_src-8b494dad6d8e92f188fb60af2db7f8277dd3974a.tar.bz2 | |
Stop keeping track of the current hovered node for accessibility.
For some reason, TalkBack isn't always trying to give accessibility focus
to a node when we send AccessibilityEvent.TYPE_VIEW_HOVER_ENTER on it, so
keep sending it as long as accessibility focus hasn't moved. Just keep track
of whether we're hovering or not as a boolean, instead.
Also, fix the logic in ContentViewCore so that MotionEvent.ACTION_HOVER_EXIT
still gets passed to BrowserAccessibilityManager, just not to the web when
touch exploration is on. We used MotionEvent.ACTION_HOVER_EXIT to know when
the finger is released, to scroll the page.
BUG=353201
Review URL: https://codereview.chromium.org/202283002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@258964 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/base/README.chromium')
0 files changed, 0 insertions, 0 deletions