Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key up events

Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key up events

Due to the way we handle keyboard events, we need to explicitly handle prevention of both key down and key up events in js.

If we do not, accelerators that happen to trigger via release e.g. the high contrast shortcut, will activate.

BUG=668771
TBR=dtseng@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2552013003
Cr-Commit-Position: refs/heads/master@{#436653}
(cherry picked from commit fa04240e9ca5c26709789a3ebfb5ed522a1d4355)

Committed: https://chromium.googlesource.com/chromium/src/+/5406e90c70e3030c25a654c5c056cf74f820bfef

[David Tseng, 2016-12-12 18:39:54]

Description was changed from

==========
Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key
up events

Due to the way we handle keyboard events, we need to explicitly handle
prevention of both key down and key up events in js.

If we do not, accelerators that happen to trigger via release e.g. the high
contrast shortcut, will activate.

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

Review-Url: https://codereview.chromium.org/2552013003
Cr-Commit-Position: refs/heads/master@{#436653}
(cherry picked from commit fa04240e9ca5c26709789a3ebfb5ed522a1d4355)
==========

to

==========
Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key
up events

Due to the way we handle keyboard events, we need to explicitly handle
prevention of both key down and key up events in js.

If we do not, accelerators that happen to trigger via release e.g. the high
contrast shortcut, will activate.

BUG=668771
TBR=dtseng@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2552013003
Cr-Commit-Position: refs/heads/master@{#436653}
(cherry picked from commit fa04240e9ca5c26709789a3ebfb5ed522a1d4355)
==========

[David Tseng, 2016-12-12 18:40:06]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2016-12-12 18:40:39]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-12 18:40:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-12 18:40:40]

CLs for remote refs other than refs/pending/heads/master must contain NOTRY=true
and NOPRESUBMIT=true in order for the CQ to process them

[David Tseng, 2016-12-12 18:52:09]

Description was changed from

==========
Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key
up events

Due to the way we handle keyboard events, we need to explicitly handle
prevention of both key down and key up events in js.

If we do not, accelerators that happen to trigger via release e.g. the high
contrast shortcut, will activate.

BUG=668771
TBR=dtseng@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2552013003
Cr-Commit-Position: refs/heads/master@{#436653}
(cherry picked from commit fa04240e9ca5c26709789a3ebfb5ed522a1d4355)
==========

to

==========
Merge to m56: Ensure spoken feedback keyboard hooks prevent re-injection of key
up events

Due to the way we handle keyboard events, we need to explicitly handle
prevention of both key down and key up events in js.

If we do not, accelerators that happen to trigger via release e.g. the high
contrast shortcut, will activate.

BUG=668771
TBR=dtseng@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2552013003
Cr-Commit-Position: refs/heads/master@{#436653}
(cherry picked from commit fa04240e9ca5c26709789a3ebfb5ed522a1d4355)

Committed:
https://chromium.googlesource.com/chromium/src/+/5406e90c70e3030c25a654c5c056...
==========

[David Tseng, 2016-12-12 18:52:10]

Committed patchset #1 (id:1) manually as
5406e90c70e3030c25a654c5c056cf74f820bfef (presubmit successful).