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

Tab title text sometimes becomes invisible when using the Light theme #19718

New Issue
Closed
opened 2026-01-31 06:51:43 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:51:43 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Apr 15, 2023).

Windows Terminal version

Commit 72d0566fa6

Windows build number

10.0.19045.2728

Other Software

No response

Steps to reproduce

  1. Build Windows Terminal from a recent commit.
  2. Start with all default settings (just to confirm that nothing else is a factor).
  3. Switch the application Theme to Light.
  4. Open a couple of cmd tabs (any shell will probably suffice).
  5. Click on the tab titles to switch between the tabs.

Expected Behavior

The tab title should remain visible when switching tabs.

Actual Behavior

As soon as the mouse button is released (after clicking on a tab), the tab title becomes invisible, possibly just rendered as black on black.

image

If you move the mouse, it should become visible again. But if you move the mouse off the tab fast enough, while it's still invisible, it can remain stuck in that invisible state.

Switching focus to another application also seems make the active tab title invisible.

I don't have this issue in the 1.17.1023 preview build.

Originally created by @j4james on GitHub (Apr 15, 2023). ### Windows Terminal version Commit 72d0566fa6d681291799e59a69168fc0483d8277 ### Windows build number 10.0.19045.2728 ### Other Software _No response_ ### Steps to reproduce 1. Build Windows Terminal from a recent commit. 2. Start with all default settings (just to confirm that nothing else is a factor). 3. Switch the application Theme to _Light_. 4. Open a couple of cmd tabs (any shell will probably suffice). 5. Click on the tab titles to switch between the tabs. ### Expected Behavior The tab title should remain visible when switching tabs. ### Actual Behavior As soon as the mouse button is released (after clicking on a tab), the tab title becomes invisible, possibly just rendered as black on black. ![image](https://user-images.githubusercontent.com/4181424/232168351-7c39a15e-54dd-4d9d-b7b4-ddba6024d6ca.png) If you move the mouse, it should become visible again. But if you move the mouse off the tab fast enough, while it's still invisible, it can remain stuck in that invisible state. Switching focus to another application also seems make the active tab title invisible. I don't have this issue in the 1.17.1023 preview build.
claunia commented 2026-01-31 06:51:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2023):

I can't help but think this is somehow related to #15150. Somehow.

No, it's not that

@zadjii-msft commented on GitHub (Apr 20, 2023): ~I can't help but think this is somehow related to #15150. Somehow.~ No, it's not that
claunia commented 2026-01-31 06:51:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2023):

Theory 2: Something fucky with tab colors post 2.8. Maybe a new resource key. Maybe a different order of application of the .Foreground() property on the tab.

It does look like

  • deselected pointer over: black ✅
  • pointer pressed: white ✅
  • selected, Pointer over: black ❌
  • selected (no pointer over): white ✅

Interesting that this isn't applying to the close button. Interesting.

@zadjii-msft commented on GitHub (Apr 20, 2023): Theory 2: Something fucky with tab colors post 2.8. Maybe a new resource key. Maybe a different order of application of the `.Foreground()` property on the tab. It does look like * deselected pointer over: black ✅ * pointer pressed: white ✅ * selected, Pointer over: black ❌ * selected (no pointer over): white ✅ Interesting that this isn't applying to the close button. Interesting.
claunia commented 2026-01-31 06:51:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2023):

that ain't right. There's no... Children? for the TabViewItem? That can't possibly be right.

Okay this is a dumb lead, but I originally was reproing this constantly on 1825ca1 but wait that was after 9b960bc. hmm. Not a lead after all.

On main (ffda8c4), I can only repro this with closing the last, active tab, which causes the previous tab to become activated, without the pointer being over it. Interesting.

@zadjii-msft commented on GitHub (Apr 20, 2023): ![](https://user-images.githubusercontent.com/18356694/233431020-f998879d-5a0d-4de4-8d65-75064ecbf830.png) that ain't right. There's no... Children? for the TabViewItem? That can't possibly be right. <hr> Okay this is a dumb lead, but I originally was reproing this _constantly_ on 1825ca1 but wait that was _after_ 9b960bc. hmm. Not a lead after all. On `main` (ffda8c4), I can only repro this with closing the last, active tab, which causes the previous tab to become activated, without the pointer being over it. Interesting. ![](https://media.tenor.com/OghEspcGUhEAAAAC/its-so-dumb-so-dumb.gif)
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 In-PR Issue-Bug Needs-Tag-Fix Product-Terminal Severity-Blocking
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#19718
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?