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.

Sign up for GitHub

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

Jump to bottom

Visible text input lag #4767

Closed
privacyguy123 opened this issue Mar 1, 2020 · 4 comments
Closed

Visible text input lag #4767

privacyguy123 opened this issue Mar 1, 2020 · 4 comments
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-Performance Performance-related issue Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@privacyguy123
Copy link

privacyguy123 commented Mar 1, 2020 •
edited
Loading

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.113]
Windows Terminal version (if applicable): Latest from Microsoft Store

Steps to reproduce

Use the Terminal!

Expected behavior

Less visible input lag within the Terminal, in both Powershell and WSL.

Actual behavior

While typing, there is visible input lag in all Windows Terminal windows.
@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 Mar 1, 2020
@zadjii-msft
Copy link
Member

Any chance you're using the retro terminal effects? I've seem personally that feature seems to introduce a bit of lag.

Is this possibly #1311?

@zadjii-msft zadjii-msft added Area-Input Related to input processing (key presses, mouse, etc.) Area-Performance Performance-related issue Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Mar 2, 2020
@privacyguy123
Copy link
Author

I'm not sure what retro terminal effects so I don't think I'm using them no!

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Mar 2, 2020
@DHowett-MSFT
Copy link
Contributor

We're doing performance and rendering work; I bet that this is going to be related to /dup #1064 and #778

@ghost
Copy link

ghost commented Mar 6, 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 Mar 6, 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 Needs-Attention The core contributors need to come back around and look at this ASAP. labels Mar 6, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-Performance Performance-related issue Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett-MSFT @zadjii-msft @privacyguy123