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

Issue 818332 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Gboard, at least in some scenarios, sends duplicate key (and other) events for a single key press in contenteditable elements.

Reported by ja...@basecamp.com, Mar 2 2018

Issue description

Steps to reproduce the problem:
1. Open https://jsfiddle.net/javan/xm518wsz/embedded/result,html/
2. Place the cursor before "Hello"
3. Press return
4. Note how many keydown, keyup, input, etc. events there are.

What is the expected behavior?
Expected behavior is Chrome 65 + GBoard should relay proper key or input events for context.

What went wrong?
Instead events relayed from Chrome 65 to Gboard show many erroneous events. It's difficult to know what events are accurate.

Did this work before? Yes Chrome Beta 65.0.3325.74

Chrome version: 65.0.3325.109  Channel: stable
OS Version: 8.1.0
Flash Version: 

I discovered this bug by testing a workaround for https://bugs.chromium.org/p/chromium/issues/detail?id=812674
 
chrome-65-return.png
121 KB View Download
Cc: rlanday@chromium.org
Components: -Blink Blink>Editing>IME UI>Input>Text>IME
Owner: changwan@chromium.org
Status: Assigned (was: Unconfirmed)
changwan@, do you have time to look into this? The behavior here seems...interesting
I'm confused by the claim that this worked better in Chrome Beta 65.0.3325.74. I just tested in 64.0.3282.137, and there are fewer events, but I still see keydown being fired twice and keyup fired thrice.

Comment 3 by ja...@javan.us, Mar 3 2018

Coworker of Jamie here. This issue was incorrectly reported as a regression, and I don't think anything changed between beta releases of Chrome 65. Chrome 64 (and earlier, most likely) also fires far too many events.

Comment 4 Deleted

Comment 5 by ja...@basecamp.com, Mar 3 2018

Hi, sorry I miscategorized it. I had not observed the behavior in an earlier version, so perhaps the fewer events firing didn't cause the error with Gboard.
Cc: dtapu...@chromium.org
Labels: -Type-Bug-Regression Needs-Bisect Type-Bug
Owner: ----
Status: Available (was: Assigned)
I think this probably correctly reflects what GBoard does. Swiftkey or samsung keyboard may exhibit a different behavior. Unfortunately, I don't have time to investigate this for now, unassigning myself.
Labels: -Needs-Bisect

Sign in to add a comment