Issue metadata
Sign in to add a comment
|
Korean IME overriden with non-QWERTY keyboard input in Chrome and newer Electron-based apps
Reported by
berm...@gmail.com,
Nov 14
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. Set up English US Dvorak as default keyboard, Korean Microsoft IME as secondary keyboard 2. Switch to Korean, then type the keys corresponding to ASDF in omnibar or any text input field What is the expected behavior? When typing the keys ASDF (leftmost 4 home-row keys), we should see ㅁㄴㅇㄹ What went wrong? Instead, in Chrome and other Electron-based apps (Atom, VS Code, Twistapp), we see 매뎌(ㅁ,ㅐ,ㄷ,ㅕ), corresponding to the keys AOEU, the four left home-row keys on a Dvorak keyboard Did this work before? Yes Over a year or more ago, on many PCs Chrome version: 70.0.3538.102 Channel: stable OS Version: 10.0 Flash Version: Alt-tabbing away and then coming back, then switching the IME sometimes makes proper input possible, but also sometimes switching back to Dvorak English is overridden. Switching off "use hardware-based acceleration when available" seems to rectify, but this quickfix is not available for other Electron-based apps. I assume this is because of two things: the Korean IME is still a hack in Windows-- instead of taking in pure keyboard codes, it's retranslating QWERTY input into the corresponding Korean. That said, this is not a problem in any other browser. My guess is that some smartypants wanted to use Dvorak or AZERTY or QWERTZ to input in Chinese Pinyin (which is not a bad idea), and told Chrome to override the current Windows IME.
,
Nov 15
Unable to reproduce the issue on reported chrome version #70.0.3538.102 using Windows 10 by following steps as per comment#0. Observed that when typing the keys ASDF in the omnibar, it got displayed as ㅁㄴㅇㄹ. Note: Tried on Mac OS 10.13.6, by changing 2-set Korean as a secondary keyboard but unable to reproduce the issue there as well. Attached screencast for reference. @reporter: Could you please review attached screencast for reference and let us know if anything is being missed here. Request to retry issue by creating a new person without any apps and extensions in it, reset all flags to default and let us know if the issue still persists. Thanks.!
,
Nov 22
Hi! Thank you for addressing this issue. Judging from your onscreen video capture, it doesn't seem like you've installed the US Dvorak keyboard, and made it your default. My picklist for languages actually say: United States-Dvorak keyboard See attached screenshot.
,
Nov 22
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 22
It also looks as if you've made the Korean IME the default input method as well. My setup is US-Dvorak first, Korean IME secondary. I am glad that this is finally getting looked at.
,
Nov 22
As I was trying to reproduce the issue, I discovered the buggy behavior is gone! Did someone fix it, either at Windows, Electron, Atom or even VS Code? This is amazing! Everything works the way it did nearly a year ago. I had resorted to stop using Chrome or Atom whenever I needed it, but using more apps that were built with Electron (the last straw was Twistapp) I decided to try to bring it to someone's attention. Thank you. First ticket was at VS Code: https://github.com/Microsoft/vscode/issues/62642 They redirected me to open a ticket here at Chromium Bugs. Then I also opened a ticket at Windows Feedback hub (since it's also an Korean IME issue, might even be solved by modernizing the Korean IME to not translate from expected QWERTY input, and take in pure Keyboard codes instead) https://aka.ms/AA373vb
,
Nov 22
@reporter: As per comment#6 the issue seems to resolved, could you please confirm if the issue can be closed from our end. Thanks.!
,
Nov 23
I am pleased to report that the buggy behavior is gone in Chrome, and every Electron-based app I use: VS Code, Atom, Twistapp, Discord. I'd love to know who fixed it, but the annoying behavior I lived for a long time now is gone. Viva la Dvorak! (http://www.dvzine.org/zine/24-cit.html) You may close this issue. Thank you for your help.
,
Nov 23
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 26
As per comment#8, the issue seems to be resolved hence closing the issue and marking it as WontFix. @reporter: Please feel free to raise a new one if the issue is seen again. Thanks.! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Nov 14