Skip to content

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

Closed

Description

@aca-ta

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.

the-first-key-pressing-ignored.mp4

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Oct 16, 2021
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Oct 16, 2021
  3. added
    Area-i18nInternationalization issues (e.g.: non-US input handling doesn't work)
    Area-InputRelated to input processing (key presses, mouse, etc.)
    Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
    on Oct 18, 2021
  4. htsnul commented on Jan 13, 2022

    @htsnul

    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.

  5. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Feb 17, 2022
  6. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Mar 10, 2022
  7. lhecker commented on Jul 9, 2025

    @lhecker
    Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-InputRelated to input processing (key presses, mouse, etc.)Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Area-i18nInternationalization issues (e.g.: non-US input handling doesn't work)Help WantedWe encourage anyone to jump in on these.Issue-BugIt either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsPriority-1A description (P1)Product-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions