Chrome Version: M65 ToT
Context(internal): b/33295713

When text input to ARC++ app is active, the current implementation 
https://cs.chromium.org/chromium/src/components/exo/keyboard.cc?type=cs&q=consumedByime&sq=package:chromium&l=56
stops sending enter and backspace key events via exo/wayland.
(To avoid double-handling by the Chrome OS Input Methods and the app.)

This causes a problem when keydown is fired while text input is inactive,
and the corresponding keyup is fired when text input is made active.
Since no keyup is received by the ARC++ inputflinger, it starts generating infinite key repeats.



The bad situation can be simply avoided by not consuming keyup events at all.
This behavior has been already there for normal character keys and didn't cause issues.