Keyboard Input Language Mismatch Causes Ctrl Key to Become Stuck (Thai Keyboard)
Hello Jump Desktop Support Team,
I would like to report a keyboard input issue related to language/input-source synchronization.
Previous behavior on Windows
When using Jump Desktop with Windows, typing works normally only when the keyboard language on the remote/client machine matches the language currently selected on the Windows host.
If the input languages do not match, the keyboard immediately behaves as if the Ctrl key is being held down continuously.
For example:
-
Client keyboard language matches Windows host language → typing works normally.
-
Client keyboard language does not match Windows host language → Ctrl appears to become stuck immediately.
This happens consistently and is directly related to the input-language mismatch.
Behavior in the latest beta
In the latest beta version, it appears that the Windows-side language handling has been changed or disabled.
However, the same problem now occurs with the Mac host input source.
If the keyboard language/input source being used remotely does not match the active input source on the Mac, the keyboard immediately behaves as if the Ctrl key is permanently held down.
The problem starts immediately after the language/input source becomes mismatched.
For example:
Mac Host: Thai
Remote keyboard: English
→ Ctrl becomes stuck immediately.
Or:
Mac Host: English / ABC
Remote keyboard: Thai
→ Ctrl becomes stuck immediately.
As soon as the input language is aligned correctly again, keyboard input returns to normal.
Important observation
This is not a random stuck-modifier issue.
It is directly triggered by a mismatch between the active keyboard/input language on the Host and the keyboard language being used on the remote device.
In the latest beta, the issue appears to have moved from Windows language handling to the Mac host input source handling.
Expected behavior
The remote keyboard should be able to type normally regardless of which input source is currently selected on the Host Mac.
Switching between Thai and English should not cause Ctrl, Command, Option, or any other modifier key to become stuck.
Actual behavior
As soon as the Host Mac input source and the remote keyboard language do not match:
Ctrl is immediately interpreted as being continuously pressed.
This makes normal typing impossible until the languages/input sources are matched again.
Please investigate the keyboard event translation and input-source synchronization in the latest beta, especially when switching between Thai and English.
This issue is consistently reproducible.
Thank you.
Please sign in to leave a comment.
Comments
0 comments