New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 762646 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

[Feedback Prestable] Event keyup is not being reconized

Project Member Reported by jainabhi...@chromium.org, Sep 6 2017

Issue description

Chrome Version : 61.0.3163.72
Device : ASUS_T00J
OS : Android 4.4.2

Developer Feedback
Hello, I'm having some issues with keyup event in HTML. I've tested this issue in Chrome Beta and Chrome, both for mobile. It seems the event keyup is not being reconized, if an input form has a character already, keyup event will not catch a special buttons, like backapace, space, enter, it will catch the last key pressed.

To reproduce this, create a input form, add a eventlistener into this form with keyup, create a function to print the keycode into html (innerHTML). Then the bug happens.

Feedback : https://listnr/report/72302167674
 
Cc: changwan@chromium.org
Labels: -Needs-Bisect -Type-Bug-Regression -M-61 Type-Bug
No evidence this is 61 regression.  I'm not sure there are enough details in this feedback report to reproduce a problem either, but cc'ing changwan@ in case he notices something.
Owner: changwan@chromium.org
Status: WontFix (was: Untriaged)
I tried https://jsfiddle.net/galmacky/pz7dnnLj/ and a slightly modified version with input tag (https://jsfiddle.net/galmacky/moL0k72d/) on stable M59, beta M61, dev M62, but I couldn't reproduce this issue. key events are sent out on composition, deletion, and key event (backspace when the text is empty and enter key on swiftkey keyboard).

Possibly a mistake by reporter. Also possible that the reporter wants the actual key code which is not supported on Android. Let me close this.

Sign in to add a comment