Erratic behavior when using input methods

[ghost]

Environment

Windows build number: Microsoft Windows [版本 10.0.18363.720]
Windows Terminal version (if applicable): 0.10.781.0

Any other software? no

Steps to reproduce

Open a terminal with Chinese IME on. Now type any pinyin, e.g. "shili" ("example"), and you see the characters suggested by the IME.

(The cursor bar should appear on the right side as mentioned in issue #3730, but it's a minor bug.)

Then hit backspace 5 times to clear the input.

Expected behavior

What you just typed in the IME should be deleted and the IME suggestion box should be closed. There shouldn't be any side effects.

Actual behavior

The suggestion box closes, but an unexpected "s" remains. What's more, while English input is still fine, you're no longer able to use IME to type in this terminal window: the suggestion box works but nothing appears in the terminal.

This also happens when you interrupt the IME, for example by clicking elsewhere, before accepting the characters.

[skyline75489]

This is a known issue. Related to #5054 and #5110 .

[ghost]

@skyline75489 Thanks for replying! I see now it's a duplicate of #5054 and there seems to be already a fix (#5109). The first-letter thing still exists, though. I'm just a student and I haven't studied much of the source code, but I think I'll fork the repo and try to build and understand it in case my computer hardware permits.

[skyline75489]

@Knowif Glad to hear that. A good practice before submitting an issue would be checking if there's any duplicate. Contributing is also welcomed.

[zadjii-msft]

Thanks for the triage pass @skyline75489!

@Knowif since you're thinking this looks like a dupe of #5054, I'm going to resolve this issue as such. If this ends up coming back after 0.11 comes out, then feel free to ping us here and we can re-open to continue the investigation. Thanks!

/dupe #5054

[ghost]

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!