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

Issue 593443 link

Starred by 1 user
Status: WontFix
Owner:
█ chongz@chromium.org
Last visit > 30 days ago
Closed: May 2016
Cc:
shuchen@chromium.org
█ suzhe@chromium.org
█ kochi@chromium.org
dtapu...@chromium.org
█ chongz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

REGRESSION: Dead key + foo produce extra keydown&keyup

Project Member Reported by chongz@chromium.org, Mar 9 2016 
Affected version: 51.0.2672.0 (build from Chromium master) (64-bit), Platform 8034.0.0
Last known working Version: 50.0.2657.0 canary (64-bit), Platform 8034.0.0

What steps will reproduce the problem?
(1) Go to https://cdn.rawgit.com/w3c/uievents/gh-pages/tools/key-event-viewer.html
(2) Switch to French keyboard layout
(3) Press '[' (a dead key) then 'q' (maps to 'a')

What is the expected output? 
Should fire 2 pairs of keydown&keyup, one pair for dead key and another for 'q'.

What do you see instead?
Fires 3 pairs of keydown&keyup.

Suspect CL http://crrev.com/1176313002 (9 months ago?? But revert it will fix.)

Comment 1 by shuchen@chromium.org, Mar 10 2016

Cc: suzhe@chromium.org kochi@chromium.org

Comment 2 by dtapu...@chromium.org, Mar 10 2016

Owner: chongz@chromium.org
Status: Assigned (was: Untriaged)
Chong is attempting to find the culprit; assigning to him for now.

Comment 3 by chongz@chromium.org, Mar 10 2016 

It seems to me that the cause is the CL mentioned in the description, but I have no idea why I can only reproduce the issue on a Chromium deployed to Chromium OS, but not on an official Chrome OS build.

Any help is appreciated.

Comment 4 by chongz@chromium.org, Mar 18 2016

Labels: -Pri-1 Pri-2

Comment 5 by chongz@chromium.org, May 11 2016

Status: WontFix (was: Assigned)
Seems no one could reproduce my issue, could be my setup problem.
►

Sign in to add a comment