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

Add an option for tabColor in the colorscheme object #14774

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

Originally created by @rashil2000 on GitHub (Aug 3, 2021).

Description of the new feature/enhancement

The default color for every new tab is either #000000 (dark theme) of #ffffff (light theme). I know there's an option to set tabColor per profile, but I think it'd be pretty neat to make it part of the colorscheme itself.

Proposed technical implementation details (optional)

Just another field in the colorscheme object. The colorscheme object already has three fields that can be overridden in the profile - foreground, background, and cursorColor. tabColor can behave similarly.

Motivation

I like having the tab background flush with the actual background (who doesn't?) so that they seem seamless. As of now it requires specifying the tabColor in each profile which uses a non-default colorscheme. The command palette allows changing colorschemes on the fly, but then you have to manually change the tabColor too.

I'd like to add that this is just a convenience feature request - not really essential.

Cheers!

Originally created by @rashil2000 on GitHub (Aug 3, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 The default color for every new tab is either `#000000` (dark theme) of `#ffffff` (light theme). I know there's an option to set `tabColor` per profile, but I think it'd be pretty neat to make it part of the colorscheme itself. # Proposed technical implementation details (optional) Just another field in the colorscheme object. The colorscheme object already has three fields that can be overridden in the profile - `foreground`, `background`, and `cursorColor`. `tabColor` can behave similarly. ## Motivation I like having the tab background flush with the actual background (who doesn't?) so that they seem seamless. As of now it requires specifying the tabColor in each profile which uses a non-default colorscheme. The command palette allows changing colorschemes on the fly, but then you have to manually change the tabColor too. I'd like to add that this is just a convenience feature request - not really essential. Cheers!
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:19:08 +00:00
claunia commented 2026-01-31 04:19:09 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Aug 3, 2021):

Alternate technical implementation

W.r.t. the motivation specified above, instead of setting the tabColor to either black or white by default, can it read the colorscheme's (either the default colorscheme or the one user has specified in the profile) background property? This behavior can also be made configurable in the form of a global boolean.

@rashil2000 commented on GitHub (Aug 3, 2021): ## Alternate technical implementation W.r.t. the motivation specified above, instead of setting the tabColor to either black or white by default, can it read the colorscheme's (either the default colorscheme or the one user has specified in the profile) background property? This behavior can also be made configurable in the form of a global boolean.
claunia commented 2026-01-31 04:19:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 4, 2021):

, instead of setting the tabColor to either black or white by default, can it read the colorscheme's (either the default colorscheme or the one user has specified in the profile) background property?

This is actually almost exactly like the implementation I have proposed (/in progress) for #5772, #3327. More specifically, this sounds like /dup #702

@zadjii-msft commented on GitHub (Aug 4, 2021): > , instead of setting the tabColor to either black or white by default, can it read the colorscheme's (either the default colorscheme or the one user has specified in the profile) background property? This is actually almost exactly like the implementation I have proposed (/in progress) for #5772, #3327. More specifically, this sounds like /dup #702
claunia commented 2026-01-31 04:19:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 4, 2021):

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 (Aug 4, 2021): 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!
claunia commented 2026-01-31 04:19:09 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Aug 4, 2021):

Oh, so does that mean that making tabColor a part of the colorscheme object is not going to get considered?

@rashil2000 commented on GitHub (Aug 4, 2021): Oh, so does that mean that making tabColor a part of the colorscheme object is not going to get considered?
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 Resolution-Duplicate
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#14774
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?