Version: 56.0.2900.0
OS: 8915.0.0

Filing in response to an internal bug b/32411164 filed for ARC.

What steps will reproduce the problem?
(1) Open Chrome OS Accessibility keyboard (Enable on-screen keyboard in settings and press the keyboard icon on the tray.)
(2) Open https://jsfiddle.net/04s0ov1u/
(3) Press 'a' key on the virtual keyboard.

What is the expected output?
In the developer console, "down" and "up" log is recorded.

What do you see instead?
Only "down" log.


@shuchen, is this an intended behavior or something that can be addressed?
(I read some bugs in the past https://bugs.chromium.org/p/chromium/issues/list?can=1&q=component%3AUI%3EInput%3EVirtualKeyboard+keyup and imagine this is not a simple matter...)

In b/32411164, the keydown without keyup resulting in an non-terminating keyrepeat since the input manager inside ARC does not receive keyup.
I believe having proper keyup event here is useful to make the a11y keyboard as a replacement of physical keyboard in touchview mode, etc.