When the input line reaches the bottom of the window, the character string of the IME conversion candidate in the input line is not displayed in the input line. #18378

Closed
opened 2026-01-31 06:12:08 +00:00 by claunia · 4 comments
Owner

Originally created by @t32ak1 on GitHub (Sep 3, 2022).

Windows Terminal version

1.14.2282.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

  1. Open a terminal window.
  2. Display something until a scroll bar appears. (ex. Repeat echo until the line reaches the bottom of the Window.)
  3. Turn on IME and display IME candidates.

Expected Behavior

Characters in the IME input state are displayed in the input line.

Actual Behavior

Characters in the IME mode are output outside the input line (probably outside the window).
IME Candidate appears Incorrectly

Originally created by @t32ak1 on GitHub (Sep 3, 2022). ### Windows Terminal version 1.14.2282.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce 1. Open a terminal window. 2. Display something until a scroll bar appears. (ex. Repeat echo until the line reaches the bottom of the Window.) 3. Turn on IME and display IME candidates. ### Expected Behavior Characters in the IME input state are displayed in the input line. ### Actual Behavior Characters in the IME mode are output outside the input line (probably outside the window). ![IME Candidate appears Incorrectly](https://user-images.githubusercontent.com/51771015/188265163-96ced641-0fd9-47ee-9609-4e4145afd0d4.gif)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:12:08 +00:00
Author
Owner

@j4james commented on GitHub (Sep 3, 2022):

I think this is probably the same issue as #13769. There's a fix committed which should be available in the next servicing release.

@j4james commented on GitHub (Sep 3, 2022): I think this is probably the same issue as #13769. There's a fix committed which should be available in the next servicing release.
Author
Owner

@t32ak1 commented on GitHub (Sep 3, 2022):

Thank you for your confirmation.

It certainly looks similar to the phenomenon reported in #13769.
Sorry for the lack of confirmation.

Thank you for your response.

@t32ak1 commented on GitHub (Sep 3, 2022): Thank you for your confirmation. It certainly looks similar to the phenomenon reported in #13769. Sorry for the lack of confirmation. Thank you for your response.
Author
Owner

@DHowett commented on GitHub (Sep 6, 2022):

Thanks for confirming! /dup #13769

@DHowett commented on GitHub (Sep 6, 2022): Thanks for confirming! /dup #13769
Author
Owner

@ghost commented on GitHub (Sep 6, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Sep 6, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18378