Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erratic behavior when using input methods #5282

Closed
Knowif opened this issue Apr 8, 2020 · 5 comments
Closed

Erratic behavior when using input methods #5282

Knowif opened this issue Apr 8, 2020 · 5 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Knowif
Copy link

Knowif commented Apr 8, 2020

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.

image

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

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 8, 2020
@skyline75489
Copy link
Collaborator

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

@Knowif
Copy link
Author

Knowif commented Apr 8, 2020

@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
Copy link
Collaborator

@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
Copy link
Member

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
Copy link

ghost commented Apr 8, 2020

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 ghost closed this as completed Apr 8, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 8, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants