starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Prevent opening new tabs when clicking in taskbar pinned app on primary monitor with Windows Terminal opened in secondary monitor #20929

New Issue
Closed
opened 2026-01-31 07:28:03 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:28:03 +00:00
Owner
Copy Link

Originally created by @cakira on GitHub (Nov 30, 2023).

Description of the new feature/enhancement

I have a setup with 2 monitors. Also, I have Windows Terminal (WT) pinned to my taskbar.
Sometimes, I move WT to the secondary monitor and I forget it is open there. Then, I want to run a command in WT, so I click the WT icon in the taskbar in the primary monitor.
Current behavior: Clicking the icon causes the Windows Terminal on the secondary monitor to pop up and open a new tab.
Desired behavior: Clicking the icon could make the Windows Terminal on the secondary monitor pop up without opening a new tab.

This request is related to #14130, but it has an opposite behavior. That ticket asks to open a new window instead of a new tab, this ticket asks to not open a new tab at all.

Proposed technical implementation details (optional)

After reading the documentation and conducting tests, I found that calling wt.exe with the command line option "focus-tab" achieves the desired behavior. However, I'm unable to configure the taskbar-pinned app to run with command line options in Windows 11. A setting to make the option "focus-tab" implicit and automatic could address this.

Originally created by @cakira on GitHub (Nov 30, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> I have a setup with 2 monitors. Also, I have Windows Terminal (WT) pinned to my taskbar. Sometimes, I move WT to the secondary monitor and I forget it is open there. Then, I want to run a command in WT, so I click the WT icon in the taskbar in the primary monitor. _Current behavior:_ Clicking the icon causes the Windows Terminal on the secondary monitor to pop up and open a new tab. _Desired behavior:_ Clicking the icon could make the Windows Terminal on the secondary monitor pop up without opening a new tab. This request is related to #14130, but it has an opposite behavior. That ticket asks to open a new window instead of a new tab, this ticket asks to not open a new tab at all. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> After reading the documentation and conducting tests, I found that calling `wt.exe` with the command line option "focus-tab" achieves the desired behavior. However, I'm unable to configure the taskbar-pinned app to run with command line options in Windows 11. A setting to make the option "focus-tab" implicit and automatic could address this.
claunia added the Issue-FeatureNeeds-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 07:28:04 +00:00
claunia commented 2026-01-31 07:28:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2023):

Hmm. I've reached out to a contact on the Taskbar team. I believe this is just "by design" with the way the taskbar currently works. I think when taskbar is set to "taskbar where window is open", I think the taskbar breaks the connection between the pinned shortcut, and the open window. I think it might end up weirder if we try and deviate from the rest of the system behavior... But who knows! Maybe this is something they're already tracking 🤷

@zadjii-msft commented on GitHub (Dec 6, 2023): Hmm. I've reached out to a contact on the Taskbar team. I believe this is just "by design" with the way the taskbar currently works. I think when taskbar is set to "taskbar where window is open", I think the taskbar breaks the connection between the pinned shortcut, and the open window. I think it might end up _weirder_ if we try and deviate from the rest of the system behavior... But who knows! Maybe this is something they're already tracking 🤷
claunia commented 2026-01-31 07:28:05 +00:00
Author
Owner
Copy Link

@cakira commented on GitHub (Dec 15, 2023):

Now, I've noticed that my browser behaves exactly as @zadjii-msft described: when pinned to my taskbar and positioned on the second monitor, clicking its icon in the taskbar opens a new browser window.

Though it's somewhat annoying to me, if this is intentional or "by design," I agree that Windows Terminal should not deviate from this pattern.
So, I'm closing this feature request.

@cakira commented on GitHub (Dec 15, 2023): Now, I've noticed that my browser behaves exactly as @zadjii-msft described: when pinned to my taskbar and positioned on the second monitor, clicking its icon in the taskbar opens a new browser window. Though it's somewhat annoying to me, if this is intentional or "by design," I agree that Windows Terminal should not deviate from this pattern. So, I'm closing this feature request.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20929
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?