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

Black text background when using PowerShell 5 #22970

New Issue
Closed
opened 2026-01-31 08:28:44 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 08:28:44 +00:00
Owner
Copy Link

Originally created by @Medard22 on GitHub (Feb 24, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

  • Open Terminal
  • Set Opacity below 100
  • Write text
  • Use Backspace to delete text

Expected Behavior

No response

Actual Behavior

Since updating to 1.22.10352.0, I have noticed a visual bug when you set opacity below 100%. Specifically, the background of white text is always 100% opaque. The same applies to deleted text.

Image

Image

Originally created by @Medard22 on GitHub (Feb 24, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce - Open Terminal - Set Opacity below 100 - Write text - Use Backspace to delete text ### Expected Behavior _No response_ ### Actual Behavior Since updating to 1.22.10352.0, I have noticed a visual bug when you set opacity below 100%. Specifically, the background of white text is always 100% opaque. The same applies to deleted text. ![Image](https://github.com/user-attachments/assets/1374dd0e-3f8d-4e63-af63-9a2d5a3bbcc4) ![Image](https://github.com/user-attachments/assets/da763d63-3dc5-476d-ae07-39003aabfa4b)
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:28:44 +00:00
claunia commented 2026-01-31 08:28:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 24, 2025):

Thanks for filing! Would you mind following the steps on our troubleshooting page for this issue/?

@DHowett commented on GitHub (Feb 24, 2025): Thanks for filing! Would you mind following the steps on our [troubleshooting page for this issue](https://learn.microsoft.com/en-us/windows/terminal/troubleshooting#black-lines-in-powershell-51-6x-70)/?
claunia commented 2026-01-31 08:28:46 +00:00
Author
Owner
Copy Link

@Medard22 commented on GitHub (Feb 25, 2025):

Ok, I had an error updating PSReadline so I did this

  • Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force
  • Update-Module PSReadline
  • Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise)

Now it´s fixed. Thank you for your help.

@Medard22 commented on GitHub (Feb 25, 2025): Ok, I had an error updating PSReadline so I did this - Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force - Update-Module PSReadline - Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise) Now it´s fixed. Thank you for your help.
claunia commented 2026-01-31 08:28:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 25, 2025):

Thanks for confirming!

@DHowett commented on GitHub (Feb 25, 2025): Thanks for confirming!
claunia commented 2026-01-31 08:28:46 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 27, 2025):

Another version of this type of color issue on v2.0 of the pwsh module which (I and many technically correct people) strongly don't recommend updating unless you test the latest version on a different machine for all your usual/typical or niche use-cases like bespoke image support in a text oriented interface that is kinda broken and so pointless for you unless you already accept the tedious compromise. And then test it more, manually, hire a tester for your frequently used pwsh modules.

Click me

I'll consider making an issue on the module's code repo. Unless they are planning a start from scratch version that loads modules from the poor LUA/non-admin accounts which are more common. maybe most common userbase because by default profiles are not admin.

The text becomes invisible for the

One Half Light

theme, from what I tested.

Steps -

0 - the obvious to enter text in the Terminal. switch to theme. and lower Opacity to 95
1 - type a word
2 - hit Space
3- type another word you won't ever see
4 - type another word you won't ever see to confirm
5 - type 5 or more spaces

Kind humble Suggestion for mostly automated tests -

0 - Figure out the requirements.
1 - Test programmatically with at least one theme from each category of expected by default theme - light, dark, purple, green, high contrast light, high contrast dark
1.1 - Figure out the requirements for 1.
1.2 - Or use a tetrad - light, dark, purple, green
2 - Verify results of 1 using eyes that are accurate within approximation to human equivalent perception.
2.1 - Use a LLM or VLM. good free local {LLM,VLM}
3 - Worry about other things affecting this, C++ sucks here if you're using every C++ thing in your code and the SDLC cycle is v rapid.

4 - Profit? 
How? 😭

Thanks and keep up the clever work team. Thanks DH, awesome profile pic.

@ghost commented on GitHub (Feb 27, 2025): Another version of this type of color issue on v2.0 of the pwsh module which (I and many technically correct people) strongly don't recommend updating unless you test the latest version on a different machine for all your usual/typical or niche use-cases like bespoke image support in a text oriented interface that is kinda broken and so pointless for you unless you already accept the tedious compromise. And then test it more, manually, hire a tester for your frequently used pwsh modules. <details><summary>Click me</summary> <p> I'll consider making an issue on the module's code repo. Unless they are planning a start from scratch version that loads modules from the poor LUA/non-admin accounts which are more common. maybe most common userbase because by default profiles are not admin. </p> </details> ---- The text becomes invisible for the ``` One Half Light ``` theme, from what I tested. # Steps - 0 - the obvious to enter text in the Terminal. switch to theme. and lower Opacity to 95 1 - type a word 2 - hit Space 3- type another word you won't ever see 4 - type another word you won't ever see to confirm 5 - type 5 or more spaces # Kind humble Suggestion for mostly automated tests - 0 - Figure out the requirements. 1 - Test programmatically with at least one theme from each category of expected by default theme - light, dark, purple, green, high contrast light, high contrast dark 1.1 - Figure out the requirements for 1. 1.2 - Or use a tetrad - light, dark, purple, green 2 - Verify results of 1 using eyes that are accurate within approximation to human equivalent perception. 2.1 - Use a LLM or VLM. `good free local {LLM,VLM}` 3 - Worry about other things affecting this, C++ sucks here if you're using every C++ thing in your code and the SDLC cycle is v rapid. ``` 4 - Profit? How? 😭 ``` Thanks and keep up the clever work team. Thanks DH, awesome profile pic.
claunia commented 2026-01-31 08:28:46 +00:00
Author
Owner
Copy Link

@schicout commented on GitHub (Apr 3, 2025):

In my case, privilege escalation was not necessary. PSReadline worked on the default execution policy.

Ok, I had an error updating PSReadline so I did this

  • Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force
  • Update-Module PSReadline
  • Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise)

Now it´s fixed. Thank you for your help.

@schicout commented on GitHub (Apr 3, 2025): In my case, privilege escalation was not necessary. PSReadline worked on the default execution policy. > Ok, I had an error updating PSReadline so I did this > > * Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force > * Update-Module PSReadline > * Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise) > > Now it´s fixed. Thank you for your help.
claunia commented 2026-01-31 08:28:47 +00:00
Author
Owner
Copy Link

@GitHub123cp commented on GitHub (Apr 4, 2025):

好的，我在更新 PSReadline 时遇到错误，所以我这样做了

  • 安装模块 -名称 PSReadLine -范围 AllUsers -AllowClobber -Force
  • Update-Module PSReadline
  • Set-ExecutionPolicy Unrestricted （因为 PSReadline 不会启动）

现在它已经修复了。感谢您的帮助。

Thank you very much for your help in solving the problem that has been bothering me for a long time.

@GitHub123cp commented on GitHub (Apr 4, 2025): > 好的，我在更新 PSReadline 时遇到错误，所以我这样做了 > > * 安装模块 -名称 PSReadLine -范围 AllUsers -AllowClobber -Force > * Update-Module PSReadline > * Set-ExecutionPolicy Unrestricted （因为 PSReadline 不会启动） > > 现在它已经修复了。感谢您的帮助。 Thank you very much for your help in solving the problem that has been bothering me for a long time.
claunia commented 2026-01-31 08:28:47 +00:00
Author
Owner
Copy Link

@Stranger-Jie commented on GitHub (Apr 7, 2025):

Updating PSReadline only resulted in the text being written white-on-white instead of adaptive the background color. see #18758 (Maybe it's a bug) .

@Stranger-Jie commented on GitHub (Apr 7, 2025): Updating PSReadline only resulted in the text being written white-on-white instead of adaptive the background color. see #18758 (Maybe it's a bug) .
claunia commented 2026-01-31 08:28:47 +00:00
Author
Owner
Copy Link

@KuRRe8 commented on GitHub (May 30, 2025):

Ok, I had an error updating PSReadline so I did this

  • Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force
  • Update-Module PSReadline
  • Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise)

Now it´s fixed. Thank you for your help.

it helps. thanks a lot

@KuRRe8 commented on GitHub (May 30, 2025): > Ok, I had an error updating PSReadline so I did this > > * Install-Module -Name PSReadLine -Scope AllUsers -AllowClobber -Force > * Update-Module PSReadline > * Set-ExecutionPolicy Unrestricted (because PSReadline won´t start otherwise) > > Now it´s fixed. Thank you for your help. it helps. thanks a lot
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-Attention 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#22970
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?