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

Window title is inconsistently updated with tab rename #9477

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

Originally created by @jtippet on GitHub (Jul 7, 2020).

Originally assigned to: @PankajBhojwani on GitHub.

Environment

Windows build number: 10.0.19041.329
Windows Terminal version (if applicable): d350a8932485f618b1658353a0573ac2422a3c36 and also repros in 1.1.1812.0

Steps to reproduce

  1. Launch Terminal
  2. Create a 2nd tab
  3. Rename the inactive tab to anything, like "bananas"
  4. Switch to the inactive tab
  5. Check the top-level window's title text (e.g., by looking at the label in the ALT+TAB experience)

Expected behavior

I'd expect the top-level window's title text to always match the active tab's title (_runtimeTabText).

Actual behavior

The top-level window's title text is just the default tab title. If you rename the tab while it's the active tab, then the top-level window title is updated... until you switch away from the tab. Once you return back to the tab, the top-level window has returned to the default title for the tab.

This is the console:
image

But this is what ALT+TAB thinks it's titled -- I'd expect it to say "bananas" at the top, not "PowerShell":
image

Originally created by @jtippet on GitHub (Jul 7, 2020). Originally assigned to: @PankajBhojwani on GitHub. # Environment ```none Windows build number: 10.0.19041.329 Windows Terminal version (if applicable): d350a8932485f618b1658353a0573ac2422a3c36 and also repros in 1.1.1812.0 ``` # Steps to reproduce 1. Launch Terminal 2. Create a 2nd tab 3. Rename the inactive tab to anything, like "bananas" 4. Switch to the inactive tab 5. Check the top-level window's title text (e.g., by looking at the label in the ALT+TAB experience) # Expected behavior I'd expect the top-level window's title text to always match the active tab's title (`_runtimeTabText`). # Actual behavior The top-level window's title text is just the default tab title. If you rename the tab while it's the *active* tab, then the top-level window title is updated... until you switch away from the tab. Once you return back to the tab, the top-level window has returned to the default title for the tab. This is the console: ![image](https://user-images.githubusercontent.com/10259764/86709258-9c059080-bfce-11ea-92fa-e81f288898a7.png) But this is what ALT+TAB thinks it's titled -- I'd expect it to say "bananas" at the top, not "PowerShell": ![image](https://user-images.githubusercontent.com/10259764/86709196-8db77480-bfce-11ea-9bd3-ffbc7300bb9a.png)
claunia commented 2026-01-31 01:55:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 10, 2020):

We should definitely go audit our event handlers and the stack that carries titles up out of the application to its final termini. Thanks!

@DHowett commented on GitHub (Jul 10, 2020): We should definitely go audit our event handlers and the stack that carries titles up out of the application to its final termini. Thanks!
claunia commented 2026-01-31 01:55:33 +00:00
Author
Owner
Copy Link

@JakubKoralewski commented on GitHub (Jul 21, 2020):

Even with this bug fixed, I could see a use case for me where I would like for the custom title tab to overwrite all other titles. Could this be a profile setting, or even better ", a more flexible solution - a little lock icon when renaming the title tab to lock that title to the window title regardless of the number of tabs inside that window/instance? Or even simpler to be able to change the window's title directly and independently from the tab title?

I got confused with lots of ideas 😅

I often open a few instances of the terminal each with a few tabs, grouped by e.g.: frontend, backend etc. specific commands so the use case I'm thinking of is labeling the window as one of the above, so when I have ten instances minimized I can quickly see which is which and binary search for the problem.

Sorry for the rant.

@JakubKoralewski commented on GitHub (Jul 21, 2020): Even with this bug fixed, I could see a use case for me where I would like for the custom title tab to overwrite all other titles. Could this be a profile setting, or even better ", a more flexible solution - a little lock icon when renaming the title tab to lock that title to the window title regardless of the number of tabs inside that window/instance? Or even simpler to be able to change the window's title directly and independently from the tab title? I got confused with lots of ideas 😅 I often open a few instances of the terminal each with a few tabs, grouped by e.g.: frontend, backend etc. specific commands so the use case I'm thinking of is labeling the window as one of the above, so when I have ten instances minimized I can quickly see which is which and binary search for the problem. Sorry for the rant.
claunia commented 2026-01-31 01:55:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 21, 2020):

@JakubKoralewski You mean something like this?
rename-tab-002

#1079, #6600, #6557

If your use case is "one window per environment", then (once this bug is fixed) you could rename the tab for each environment, and the window title should reflect the active tab's title.

Otherwise, there's also #4183 which looks like it's related

@zadjii-msft commented on GitHub (Jul 21, 2020): @JakubKoralewski You mean something like this? ![rename-tab-002](https://user-images.githubusercontent.com/18356694/88065433-34088b80-cb32-11ea-90a8-2a46b4a0b390.gif) #1079, #6600, #6557 If your use case is "one window per environment", then (once this bug is fixed) you could rename the tab for each environment, and the window title should reflect the active tab's title. Otherwise, there's also #4183 which looks like it's related
claunia commented 2026-01-31 01:55:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 13, 2020):

:tada:This issue was addressed in #7119, which has now been successfully released as Windows Terminal Preview v1.2.2234.0.🎉

Handy links:

@ghost commented on GitHub (Aug 13, 2020): :tada:This issue was addressed in #7119, which has now been successfully released as `Windows Terminal Preview v1.2.2234.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.2.2234.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Area-UserInterface good first issue Help Wanted Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal Resolution-Fix-Committed
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#9477
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?