Fire accessibility hover events when the touch exploration flag is set.

Fire accessibility hover events when the touch exploration flag is set.

On Chrome OS, when spoken feedback is enabled we change the touch screen
interaction model so that tapping or exploring the screen with one finger
sends a mouse move event with a special touch accessibility flag set.
This already fires the right accessibility events in 'views'.

Finish hooking this up for native web accessibility by propagating the input
event flag to Blink, and posting a 'hover' accessibility event on the target
when that flag is set.

BUG=513713
Committed: https://crrev.com/14b7078b451812e1c3745993e79ec1634047ea68
Cr-Commit-Position: refs/heads/master@{#351367}

[dmazzoni, 2015-09-28 19:24:14]

dmazzoni@chromium.org changed reviewers:
+ mkwst@chromium.org, plundblad@chromium.org, sadrul@chromium.org

[dmazzoni, 2015-09-28 19:24:14]

mkwst: all of the Blink code
plundblad: content/browser/accessibility (the browser test)
sadrul: ui/events/blink

[Mike West, 2015-09-29 07:10:36]

Blink bits LGTM.

[Peter Lundblad, 2015-09-29 09:48:14]

browsertest lgtm

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
File content/browser/accessibility/touch_accessibility_aura_browsertest.cc
(right):

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
content/browser/accessibility/touch_accessibility_aura_browsertest.cc:64:
CHECK(manager);
nit: use ASSERT* in tests.

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
content/browser/accessibility/touch_accessibility_aura_browsertest.cc:99:
CHECK(child);
nit: use ASSERT/EXPECT in tests?

[sadrul, 2015-09-29 15:14:11]

lgtm

[dmazzoni, 2015-09-29 17:10:05]

The CQ bit was checked by dmazzoni@chromium.org

[dmazzoni, 2015-09-29 17:10:06]

The patchset sent to the CQ was uploaded after l-g-t-m from mkwst@chromium.org,
plundblad@chromium.org, sadrul@chromium.org
Link to the patchset: https://codereview.chromium.org/1375703002/#ps40001
(title: "Use asserts instead of checks in test")

[commit-bot: I haz the power, 2015-09-29 17:11:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1375703002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1375703002/40001

[dmazzoni, 2015-09-29 17:11:28]

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
File content/browser/accessibility/touch_accessibility_aura_browsertest.cc
(right):

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
content/browser/accessibility/touch_accessibility_aura_browsertest.cc:64:
CHECK(manager);
On 2015/09/29 09:48:14, Peter Lundblad wrote:
> nit: use ASSERT* in tests.

Done.

https://codereview.chromium.org/1375703002/diff/20001/content/browser/accessi...
content/browser/accessibility/touch_accessibility_aura_browsertest.cc:99:
CHECK(child);
On 2015/09/29 09:48:14, Peter Lundblad wrote:
> nit: use ASSERT/EXPECT in tests?

Done.

[commit-bot: I haz the power, 2015-09-29 19:00:43]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-09-29 19:01:55]

Patchset 3 (id:??) landed as
https://crrev.com/14b7078b451812e1c3745993e79ec1634047ea68
Cr-Commit-Position: refs/heads/master@{#351367}