starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

the first key pressing is sometimes ignored when writing with Japanese IME. #15560

New Issue
Closed
opened 2026-01-31 04:42:00 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:42:00 +00:00
Owner
Copy Link

Originally created by @aca-ta on GitHub (Oct 16, 2021).

Windows Terminal version (or Windows build number)

10.0.22000.282 1.10.2714.0

Other Software

No response

Steps to reproduce

Write chacacters in romaji mode using Microsoft IME.

Expected Behavior

No response

Actual Behavior

For example, when typing the word sushi/すし, pressing the key 's', 'u', 's', 'h', 'i'. and press enter key to confirm the converted characters.
it is expected to be typed すし, but the first pressing 's' is ignored and typed うし, the character that should be typed when pressing 'u', 's', 'h', 'i'.
it doesn't occur except for the first keystroke. when typing sushi/すし, it only occures on the first 's' pressing.
I try with Google Japanese Input and Microsft IME and it occures with both.
it occures about once every ten times.
it doesn't occur when writing English.
and it doesn't occur with other terminals such as PuTTY or vscode terminal.

https://user-images.githubusercontent.com/5401476/137604003-33305c58-d18e-49c5-801d-280e2dd5fd84.mp4

Originally created by @aca-ta on GitHub (Oct 16, 2021). ### Windows Terminal version (or Windows build number) 10.0.22000.282 1.10.2714.0 ### Other Software _No response_ ### Steps to reproduce Write chacacters in romaji mode using Microsoft IME. ### Expected Behavior _No response_ ### Actual Behavior For example, when typing the word `sushi/すし`, pressing the key 's', 'u', 's', 'h', 'i'. and press enter key to confirm the converted characters. it is expected to be typed すし, but the first pressing 's' is ignored and typed `うし`, the character that should be typed when pressing 'u', 's', 'h', 'i'. it doesn't occur except for the first keystroke. when typing `sushi/すし`, it only occures on the first 's' pressing. I try with Google Japanese Input and Microsft IME and it occures with both. it occures about once every ten times. it doesn't occur when writing English. and it doesn't occur with other terminals such as PuTTY or vscode terminal. https://user-images.githubusercontent.com/5401476/137604003-33305c58-d18e-49c5-801d-280e2dd5fd84.mp4
claunia commented 2026-01-31 04:42:03 +00:00
Author
Owner
Copy Link

@htsnul commented on GitHub (Jan 13, 2022):

The problem occurs when the next IME input is started before the Enter key-up of the immediately preceding IME confirmation.

The first "s" of the second "sushi" is always missing in the following steps:

  1. "s" key down & up
  2. "u" key down & up
  3. "s" key down & up
  4. "h" key down & up
  5. "i" key down & up
  6. Enter key down
  7. "s" key down
  8. Enter key up
  9. "s" key up
  10. "u" key down & up
  11. "s" key down & up
  12. "h" key down & up
  13. "i" key down & up

You can avoid the problem by using Ctrl-M instead of Enter to confirm the IME.

@htsnul commented on GitHub (Jan 13, 2022): The problem occurs when the next IME input is started before the Enter key-up of the immediately preceding IME confirmation. The first "s" of the second "sushi" is always missing in the following steps: 1. "s" key down & up 2. "u" key down & up 3. "s" key down & up 4. "h" key down & up 5. "i" key down & up 6. Enter key down 7. "s" key down 8. Enter key up 9. "s" key up 10. "u" key down & up 11. "s" key down & up 12. "h" key down & up 13. "i" key down & up You can avoid the problem by using Ctrl-M instead of Enter to confirm the IME.
claunia commented 2026-01-31 04:42:03 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 9, 2025):

I suspect this got resolved with the IME rewrite in #17067. Let me know if I got that wrong.

@lhecker commented on GitHub (Jul 9, 2025): I suspect this got resolved with the IME rewrite in #17067. Let me know if I got that wrong.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-i18n Area-Input Area-TerminalControl Help Wanted Issue-Bug Needs-Tag-Fix Priority-1 Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15560
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?