Labels: Needs-Triage-M125

The same is true for Chinese

Same here, keydown event not trigger with Chinese IME. Some more info:

1. only broken on Windows. it's still working on Mac (arm64)
2. when chrome loses focus and gets focus again (switching to another application then back to chrome) , it then works as normal

Tested the issue on reported chrome version #125.0.6422.61 using Win 10 as per comment#1

Steps to reproduce:
---------------------------
1.Launched chrome browser
2.Opened given link: https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_event_key_key
3.Press a english word on the keyboard in the input field and The key was displaying in english
4.Changed keyboard language into Korean and Press a korean word on the keyboard in the input field
5.Observed "The key was" displaying nothing
6.In M114, Press a korean word on the keyboard in the input field and Observed "The key was": Process

Attaching screencast for reference

Reporter@ Could you please review the attached screencast and let us know if anything being missed here and please confirm if point:5 is the issue you are pointing to?and confirm M114 behaviour is bad/actual behaviour?  

Thanks..!!

* 100% way to reproduce the bug
1. Right-click to open the context menu, and close it.
2.  Enter Korean characters to <input> field.  Keydown event is not triggering. (English or numeric inputs will still trigger the keydown event.)

* more information
After opening and closing browser dialogs such as the context menu, toast menu, or bookmark menu, the keydown event fails to trigger for Korean characters

This issue is also happening for Japanese.

I have the same problem on my Korean site. Sometimes the keyup event doesn't fire.

ver.125.0.6422.113 / Japanese
--
I have also been having the same problem with my customer’s web system for the past 10 days.
When IME is enabled, the keydown “Process” event does not occur, and the system does not operate properly.
I hope for a quick fix.

--

> 1. Right-click to open the context menu, and close it.
> 2. when chrome loses focus and gets focus again (switching to another application then back to chrome) , it then works as normal

I was able to reproduce that method in my environment as well.

ver 125.0.6422.113/ korean

I have the same problem .

https://domeventviewer.com/key-event-viewer-ce.html
Test video and capture are attached.

Keydown/up event does not occur in hangle key mode.

Same here.

At first I thought there might be a problem with the code written.

So I tracked down the code that was relevant to event bubbling, including all the libraries in use.

But that wasn't the problem.

Whether a problem occurs or not is random, and when a problem occurs, Google Inspector's event listener breakpoint is not executed.

In the end, I realized that it wasn't a problem with writing user code, but rather Chrome's inability to generate events.

When this problem occurs, if you select another window to lose focus and then restore it, it will work normally.

Could it be because Windows suddenly changed the IME function? Or is this a problem that occurs starting with the new Chrome version?

The same problem occurs in Edge, which uses the same series of engines.

On the other hand, Firefox is working normally.

Disabling that feature in my program is a huge problem. I hope it can be resolved quickly.

There's a new Chromium version (v126) and it seems the issue is fixed at least for Japanese input.

The issue also for Korean has been fixed in new Chromium version 126. so update Chrome or Edge Browser to  v126.

Is it true that the bug has been fixed in the latest browser?
The keydown event still occurs intermittently?
I think it's okay to render for the first time, but it doesn't seem to work after a refresh.
Edge browser does not work at all
chrome 126.0.6478.62

Reporter@ - As per latest comments issues seems to be working fine in google chrome. So can we close the issue and mark this as won't fix?

Thanks..!!

chrome 126.0.6478.62

The issue still occurs intermittently.

https://domeventviewer.com/key-event-viewer-ce.html
Test video and capture are attached.

Please check again

https://issues.chromium.org/u/1/issues/342202215 
I think it was reopened because the bug occurred again after it was fixed.
But there has been no progress since reopening.
I'm curious on what basis people say that bugs have been fixed.

Tested the issue on chrome version #126.0.6478.62 using Windows 10, windows 11 arm64 as per comment#17

Steps to reproduce
================
1) Launched chrome
2) Opened https://domeventviewer.com/key-event-viewer-ce.html
3) IME enabled for korean and input given
Observed Keydown/up events are fired.

@Reporter: Could you please review the attached screencast and let us know if anything being missed here.

Thanks..!!

@Reporter: Could you please try to reproduce the issue on latest chrome stable and let us know if the issue still exists. You can download latest chrome builds here:
https://www.chromium.org/getting-involved/dev-channel

Thanks..!!

Gentle reminder

 Reporter@ Could you kindly provide your input as mentioned in comment #20? Please note that the issue will be closed if there is no response within 30 days.

Thank you!