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

Activating terminal by clicking on the tab does not set input focus #9707

Closed
randomascii opened this issue Apr 5, 2021 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@randomascii
Copy link

Windows Terminal version (or Windows build number)

1.6.10571.0

Other Software

No response

Steps to reproduce

When I activate the Windows Terminal it is because I want to type into it. However if I activate the Windows Terminal by clicking on the tab (i.e.; the tab-switcher component at the top of the window) then input focus is not set and will actually be taken away.

To be more precise, if I click on the tab-switcher for the current tab then focus is taken away. If I click on a different tab then focus is set.

Expected Behavior

When I click on a tab-switcher, whether to give the terminal focus or just because I feel like it, input focus should be set to that tab. The cursor should flash and any characters that I type should be displayed.

Actual Behavior

When I click on the tab-switcher for the currently selected tab then input focus is turned off, the flashing cursor goes away, and my keystrokes go nowhere.

@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 5, 2021
@j4james
Copy link
Collaborator

j4james commented Apr 5, 2021

This sounds like issue #3609.

@zadjii-msft
Copy link
Member

Sure is!

/dup #3609

@ghost
Copy link

ghost commented Apr 5, 2021

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 5, 2021
@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 5, 2021
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