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

Taskbar icon creates new terminal when restoring from notification area #21321

New Issue
Closed
opened 2026-01-31 07:40:35 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:40:35 +00:00
Owner
Copy Link

Originally created by @JVimes on GitHub (Feb 27, 2024).

Windows Terminal version

1.20.10303.0

Windows build number

10.0.19045.0

Other Software

n/a

Steps to reproduce

  1. Pin WT to taskbar
  2. Enable "Hide Terminal in the notification area when it is minimized"
  3. Minimize
  4. Click the WT taskbar icon

Expected Behavior

Restore the window from notification area (no new terminal tab).

Actual Behavior

Window is restored with a new terminal tab.

Originally created by @JVimes on GitHub (Feb 27, 2024). ### Windows Terminal version 1.20.10303.0 ### Windows build number 10.0.19045.0 ### Other Software n/a ### Steps to reproduce 1. Pin WT to taskbar 2. Enable "Hide Terminal in the notification area when it is minimized" 3. Minimize 4. Click the WT taskbar icon ### Expected Behavior Restore the window from notification area (no new terminal tab). ### Actual Behavior Window is restored with a new terminal tab.
claunia added the Resolution-By-DesignNeeds-TriageIssue-Bug labels 2026-01-31 07:40:35 +00:00
claunia commented 2026-01-31 07:40:44 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 28, 2024):

Thanks for filing. This is consistent with how other multi-instance apps are hidden in the tray. The taskbar does not know that Terminal is running, so it ends up launching a new instance.

Clicking the taskbar icon creates the new instance, whereas the notification area icon can be used to bring it back.

@carlos-zamora commented on GitHub (Feb 28, 2024): Thanks for filing. This is consistent with how other multi-instance apps are hidden in the tray. The taskbar does not know that Terminal is running, so it ends up launching a new instance. Clicking the taskbar icon creates the new instance, whereas the notification area icon can be used to bring it back.
claunia commented 2026-01-31 07:40:46 +00:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Feb 29, 2024):

Thank you @carlos-zamora, but that's not really true.

  • Restoring a minimized window doesn't add a new tab to it. Restoring a hidden window shouldn't. It's the same case to the user.
  • The taskbar behavior is fine because WT can end the superfluous instance. We know because the "attach to recent window" feature works.

I hope you'll consider reopening this issue.

@JVimes commented on GitHub (Feb 29, 2024): Thank you @carlos-zamora, but that's not really true. - Restoring a minimized window doesn't add a new tab to it. Restoring a hidden window shouldn't. It's the same case to the user. - The taskbar behavior is fine because WT can end the superfluous instance. We know because the "attach to recent window" feature works. I hope you'll consider reopening this issue.
claunia commented 2026-01-31 07:40:46 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 4, 2024):

You're not restoring a minimized window though, because in your example the terminal is not minimized to the taskbar. Instead it's hidden (!= minimized) in the notification area. This distinction is important, because "restoring" a window from the taskbar obviously only works if there's a window in the taskbar in the first place. But you don't have a window in the taskbar, you only have a pinned application.

You're right though that some application work differently. Steam for instance allows you to click its pinned symbol and restore the main window. But that's different from us, because unlike Steam, we're a tabbed, multi-window application and so there's no single window for us to restore. In fact, we can't even tell what your intention was (restore VS open a new tab), because clicking on a pinned application in the taskbar is identical to running it with Win+R or from the start menu.

@lhecker commented on GitHub (Mar 4, 2024): You're not restoring a minimized window though, because in your example the terminal is not minimized to the taskbar. Instead it's hidden (!= minimized) in the notification area. This distinction is important, because "restoring" a window from the taskbar obviously only works if there's a window in the taskbar in the first place. But you don't have a window in the taskbar, you only have a pinned application. You're right though that some application work differently. Steam for instance allows you to click its pinned symbol and restore the main window. But that's different from us, because unlike Steam, we're a tabbed, multi-window application and so there's no single window for us to restore. In fact, we can't even tell what your intention was (restore VS open a new tab), because clicking on a pinned application in the taskbar is identical to running it with Win+R or from the start menu.
claunia commented 2026-01-31 07:40:48 +00:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Mar 4, 2024):

I see, but there's a conflict in semantics between clicking the minimize title bar button and restoring via global-summon and/or clicking an inactive taskbar icon.

I think it's undesirable to, starting with tabs open, click minimize, then have my window come back with an additional tab. I think it's better to solve the conflict by not keeping the new instance.

Just my 2c, I guess.

@JVimes commented on GitHub (Mar 4, 2024): I see, but there's a conflict in semantics between clicking the minimize title bar button and restoring via global-summon and/or clicking an inactive taskbar icon. I think it's undesirable to, starting with tabs open, click minimize, then have my window come back with an additional tab. I think it's better to solve the conflict by not keeping the new instance. Just my 2c, I guess.
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-Bug Needs-Triage Resolution-By-Design
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#21321
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?