[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818304#comment-17818304
 ] 

maeda577 commented on GUACAMOLE-1004:
-------------------------------------

To test the behavior of the Japanese key, I created a very simple test HTML.
https://gist.github.com/maeda577/4e3e5df2065db90da14c2325709d1bde

And I have tested the Japanese IME keys on Windows and got the following 
results.

Local client: Windows 11
RDP server: Windows 11

||KeyName (Japanese)||JS 
KeyboardEvent.key||ScanCode||Modifier||X11keysym||KeyupReliable 
*1||WorksInTextArea *2||Note||
|Hankaku/Zenkaku (半角/全角)|Zenkaku|0x29|-|0xFF28|false|false|Zenkaku and Hankaku 
events occur alternately.|
|Hankaku/Zenkaku (半角/全角)|Hankaku|0x29|-|0xFF29|false|false|Zenkaku and Hankaku 
events occur alternately.|
|Kanji (漢字)|KanjiMode|0x29|Alt|0xFF21|true|true||
|Eisu (英数)|Alphanumeric|0x3A|-|0xFF30|false|false||
|CapsLock|CapsLock|0x3A|Shift|0xFFE5|true|true||
|Muhenkan (無変換)|NonConvert|0x7B|-|0xFF22|true|false||
|Henkan (変換)|Convert|0x79|-|0xFF23|true|false||
|Hiragana (ひらがな)|Hiragana|0x70|-|0xFF25|false|false||
|Katakana (カタカナ)|Katakana|0x70|Shift|0xFF26|false|false||
|Romaji (ローマ字)|KanaMode|0x70|Alt|0xFF2D|false|false|KanaMode and Romaji events 
occur alternately.|
|Romaji (ローマ字)|Romaji|0x70|Alt|0xFF24|false|false|KanaMode and Romaji events 
occur alternately.|

*1: Whether KeyUp occurs normally. Some IME keys occur KeyDown and KeyUp 
separately.
*2: If false, Windows OS will handle the key event and WebBrowser can't handle 
it. (Similar to the Alt+Tab issue. GUACAMOLE-1484)

As shown in the table, almost all IME keys are handled by Windows OS. So I have 
no idea to fix Zenkaku/Hankaku probrem...


I also tested on Ubuntu 22.04 and got the following results.

Local client: Ubuntu 22.04 Desktop
RDP server: Windows 11

||KeyName (Japanese)||JS 
KeyboardEvent.key||ScanCode||Modifier||X11keysym||KeyupReliable 
*1||WorksInTextArea *2||
|Hankaku/Zenkaku (半角/全角)|ZenkakuHankaku|0x29|-|0xFF2A|true|true|
|Kanji (漢字)|KanjiMode|0x29|Alt|0xFF21|true|true|
|Eisu (英数)|Alphanumeric|0x3A|-|0xFF30|true|true|
|CapsLock|CapsLock|0x3A|Shift|0xFFE5|true|true|
|Muhenkan (無変換)|NonConvert|0x7B|-|0xFF22|true|true|
|Henkan (変換)|Convert|0x79|-|0xFF23|true|true|
|Hiragana (ひらがな)|HiraganaKatakana|0x70|-|0xFF27|true|true|
|Romaji (ローマ字)|Romaji|0x70|Alt|0xFF24|true|true|

All IME keys worked in WebBrowser! I modified the keymap for 
guacamole-client/guacamole-server and the IME keys worked fine on Ubuntu. I 
will send a PR in the near future.

> Some keyboard input is not passed to the RDP server.
> ----------------------------------------------------
>
>                 Key: GUACAMOLE-1004
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1004
>             Project: Guacamole
>          Issue Type: Bug
>            Reporter: Kazuhiko Tanaka
>            Priority: Minor
>
>     I entered the "Zenkaku_Hankaku" key, "Capslock" key, and "Hiragana" key, 
> but they were not passed to the RDP server.  
>     Entering these keys affects the browser's IME.  Perhaps Guacamole does 
> not handle these keys properly.  
>     If enter the "Zenkaku_Hankaku" key in a Japanese browser, "Zenkaku (keyup 
> 243 and keydown 244)" and "Hankaku (keyup 244 and keydown 243)" will be 
> entered alternately, so you need to obtain both.  
>     Also, when the text area was selected, JavaScript could not get "keydown" 
> and only get "keyup" in some cases.  This may also be relevant.  
>     In particular, the "Zenkaku_Hankaku" key is a very important key for OS 
> in Japanese environment.  If the "Zenkaku_Hankaku" key cannot be entered, 
> nothing can be done.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to