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

Transparent background for text set to a black background in PowerShell #12816

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

Originally created by @Johbii on GitHub (Mar 2, 2021).

Environment

Windows build number: 10.0.18363.778
Windows Terminal version (if applicable): 1.6.10571.0

Any other software?
Powershell version: 5.1.18362.752

Steps to reproduce

  1. Open a PowerShell instance in Windows Terminal
  2. Enter Write-Error -Message "anything" (or otherwise receive an error/warning/any message with a black background)

Expected behavior

screenshot of PowerShell with background colors working

Critical error messages and warning messages are outlined with a black background to be more readable and noticeable compared with regular output (as is default with PowerShell).

Actual behavior

screenshot of Windows Terminal with colors not working

Any text highlighted with a black background is made transparent/changed to the color of the terminal background.

Notice 40m is black on the old console host but not in Windows Terminal.

Originally created by @Johbii on GitHub (Mar 2, 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363.778 Windows Terminal version (if applicable): 1.6.10571.0 Any other software? Powershell version: 5.1.18362.752 ``` # Steps to reproduce 1. Open a PowerShell instance in Windows Terminal 2. Enter `Write-Error -Message "anything"` (or otherwise receive an error/warning/any message with a black background) # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> ![screenshot of PowerShell with background colors working](https://user-images.githubusercontent.com/30395979/109684877-9caff000-7b78-11eb-8354-b5087293f06c.PNG) Critical error messages and warning messages are outlined with a black background to be more readable and noticeable compared with regular output (as is default with PowerShell). # Actual behavior <!-- What's actually happening? --> ![screenshot of Windows Terminal with colors not working](https://user-images.githubusercontent.com/30395979/109685001-ba7d5500-7b78-11eb-9c12-0e4b35901200.PNG) Any text highlighted with a black background is made transparent/changed to the color of the terminal background. Notice 40m is black on the old console host but not in Windows Terminal.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:25:43 +00:00
claunia commented 2026-01-31 03:25:44 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 6, 2021):

Quoting DHowett from issue https://github.com/microsoft/terminal/issues/9115#issuecomment-777715415:

Unfortunately, this is by design. PowerShell erroneously tells us to use a black background so often that it would cause there to be black streaks across the display (even if the terminal background was set to white or acrylic transparency.)

We had to disable black for PowerShell, specifically. #6810. Tracking the "fix" in /dup #6807.

@j4james commented on GitHub (Mar 6, 2021): Quoting DHowett from issue https://github.com/microsoft/terminal/issues/9115#issuecomment-777715415: > Unfortunately, this is by design. PowerShell erroneously tells us to use a black background _so often_ that it would cause there to be black streaks across the display (even if the terminal background was set to white or acrylic transparency.) > > We had to disable black for PowerShell, specifically. #6810. Tracking the "fix" in /dup #6807.
claunia commented 2026-01-31 03:25:44 +00:00
Author
Owner
Copy Link

@Johbii commented on GitHub (Mar 7, 2021):

Quoting DHowett from issue #9115 (comment):

Unfortunately, this is by design. PowerShell erroneously tells us to use a black background so often that it would cause there to be black streaks across the display (even if the terminal background was set to white or acrylic transparency.)
We had to disable black for PowerShell, specifically. #6810. Tracking the "fix" in /dup #6807.

Oh OK, thanks for responding. Sorry for the dupe I wasn't aware of the issue.

@Johbii commented on GitHub (Mar 7, 2021): > > > Quoting DHowett from issue [#9115 (comment)](https://github.com/microsoft/terminal/issues/9115#issuecomment-777715415): > > > Unfortunately, this is by design. PowerShell erroneously tells us to use a black background _so often_ that it would cause there to be black streaks across the display (even if the terminal background was set to white or acrylic transparency.) > > We had to disable black for PowerShell, specifically. #6810. Tracking the "fix" in /dup #6807. Oh OK, thanks for responding. Sorry for the dupe I wasn't aware of the issue.
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 Needs-Tag-Fix Needs-Triage
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#12816
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?