Click on tab ... focus ...? #11895

Closed
opened 2026-01-31 03:00:28 +00:00 by claunia · 3 comments
Owner

Originally created by @vefatica on GitHub (Dec 26, 2020).

Environment

Microsoft Windows 10 Pro for Workstations
10.0.19042.685 (2009, 20H2)
WindowsTerminalPreview_1.5.3242.0_x64

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

When working in a shell in WT, left-click on the desktop, then left-click on the tab of the shell you were working in.

Expected behavior

The shell in the clicked tab should have input focus; i.e., you can continue working there.

Actual behavior

That shell does not get input focus.

In contrast, if, after clicking the desktop, you click the tab of another shell in WT (one you were not working in) the shell of the clicked-on tab does get input focus.

It's annoying, especially since I consider the tab to be THE way to select the shell in which to work.

I figure this must be a duplicate. I searched a little and came up with nothing.

Originally created by @vefatica on GitHub (Dec 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Microsoft Windows 10 Pro for Workstations 10.0.19042.685 (2009, 20H2) WindowsTerminalPreview_1.5.3242.0_x64 ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce When working in a shell in WT, left-click on the desktop, then left-click on the tab of the shell you were working in. <!-- A description of how to trigger this bug. --> # Expected behavior The shell in the clicked tab should have input focus; i.e., you can continue working there. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior That shell does not get input focus. <!-- What's actually happening? --> In contrast, if, after clicking the desktop, you click the tab of another shell in WT (one you were not working in) the shell of the clicked-on tab does get input focus. It's annoying, especially since I consider the tab to be **THE** way to select the shell in which to work. I figure this must be a duplicate. I searched a little and came up with nothing.
claunia added the Resolution-Duplicate label 2026-01-31 03:00:28 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Dec 26, 2020):

Perhaps https://github.com/microsoft/terminal/issues/3609.

@KalleOlaviNiemitalo commented on GitHub (Dec 26, 2020): Perhaps <https://github.com/microsoft/terminal/issues/3609>.
Author
Owner

@DHowett commented on GitHub (Dec 26, 2020):

Yes, this is a /dupe of #3609 and a second issue titled something like "focus moves weirdly ..."

@DHowett commented on GitHub (Dec 26, 2020): Yes, this is a /dupe of #3609 and a second issue titled something like "focus moves weirdly ..."
Author
Owner

@ghost commented on GitHub (Dec 26, 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 commented on GitHub (Dec 26, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11895