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

Issue 706672 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

PreventDefault of keydown event does not work when typing Hangul

Reported by dap...@gmail.com, Mar 30 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36

Steps to reproduce the problem:
1. Write JS code to preventDefault on keydown event.
2. In Microsoft IME, set to Hangul mode and enter Hangul.
3. Letters appear.

What is the expected behavior?
When I test it in English, I can not see the letter. Hangul should not be displayed like English.

What went wrong?
After calling preventDefault on keydown, subsequent events, compositionstart, compositionupdate, input are generated and the characters are also displayed.

Did this work before? No 

Chrome version: 57.0.2987.110  Channel: stable
OS Version: 10.0
Flash Version: 

This is a problem from version 56. (56.0.2924.87)
 
test_hangul_prevent_default.html
1002 bytes View Download
Components: -Blink Blink>Editing>IME

Comment 2 by yosin@chromium.org, Apr 6 2017

Owner: changwan@chromium.org
Status: Assigned (was: Unconfirmed)
changwan@, could you help study this issue? Since I'm not sure how to use Korean-IME.

Comment 3 by dap...@gmail.com, Apr 20 2017

I wonder if this is going on.
When will it be done?

Comment 4 by dap...@gmail.com, May 11 2017

Please let me know your processing plan. In my application, which provides Korean editing, this bug is causing serious problems with features that worked well in versions prior to version 55.
Labels: Needs-Bisect
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on windows 10 using chrome stable #58.0.3029.110 & Canary#60.0.3096.0 as per steps & html file provided in comment#0.
Observations:
------------
1.When we type in English (keyboard selected as English),seen letters in english.
2.When we type in Korean (keyboard selected as Korean),seen letters in Korean.

Could you please check the issue by upgrading to the latest chrome stable version & let us know your observations on the same & if we miss any steps to reproduce the issue.

Please find the attached screencast fro reference.

Thanks in advance..!!
706672.mp4
4.2 MB View Download
comment #0 did not mention, but you need to hold mouse to reproduce this issue. Sorry forgot to mention it.

Comment 8 by yewon...@gmail.com, May 15 2017

'preventDefault()' is not working on mouseDown at hangle IME mode.
706672_.avi
7.9 MB Download

Comment 9 by dap...@gmail.com, May 16 2017

I have found similar bugs in the past. https://bugs.chromium.org/p/chromium/issues/detail?id=9883
At that time, it was Katakana, and now it is Hangul.
Please refer to this link to expedite the current bug.
jmukthavaram@, could you try bisecting again? Thanks.
Cc: ligim...@chromium.org
Labels: -Needs-Feedback Needs-Triage-M62
Team , please triage and bisect.
Labels: -Needs-Bisect -Needs-Triage-M62 M-62 OS-Linux OS-Mac
Able to reproduce the issue on Windows 10,Mac 10.12.6 & Ubuntu 14.04 using chrome reported version-57.0.2987.110,stable-60.0.3112.78 & Canary-62.0.3172.2 as per video provided in comment#8 & html file.

Able to see the typed letters in Hangul(korean) when user hold mouse where as in english no letters are displayed.

Same issue observed from M45 builds to latest canary.Could some one from dev team please look into this issue.

Please find the attached screencast for reference .
Thanks..!!
706672.mp4
780 KB View Download
Labels: Pri-3
Owner: rlanday@chromium.org
Cc: rlanday@chromium.org
Owner: ----
Status: Available (was: Assigned)
I filed a spec bug for this: https://github.com/w3c/uievents/issues/180

Currently, preventDefault() of keydown event is declared as reported. However, no browser does such behavior at least on desktop OSes.  So, changing the behavior causes breaking backward compatibility for all browsers.  I think that this doesn't make sense.

Additionally, from point of view of a developer of Gecko/Firefox, dispatching keydown event after sending it to IME is really helpful, especially on Windows. So, I suggested to change the declaration of the spec in the spec bug.

Sign in to add a comment