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

weird black background when pressing space in windows legacy powershell #22932

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

Originally created by @canh25xp on GitHub (Feb 17, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.19045.0

Other Software

powershell legacy version 5.1.19041.5369 no Profile.

Steps to reproduce

Open powershell(legacy) in the terminal and press space.

Expected Behavior

No black background should not appear.

Actual Behavior

A black background is appear when ever a space is enter, as shown in the image below.

Image

This only happends with legacy version of powershell.

Using any theme other than pitch black background theme results in this behaviour.

The previous version of windows terminal 1.21.3231.0 does not have this problem.

Originally created by @canh25xp on GitHub (Feb 17, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.19045.0 ### Other Software powershell legacy version `5.1.19041.5369` no Profile. ### Steps to reproduce Open powershell(legacy) in the terminal and press space. ### Expected Behavior No black background should not appear. ### Actual Behavior A black background is appear when ever a space is enter, as shown in the image below. ![Image](https://github.com/user-attachments/assets/2420e614-f67c-4fab-9c8c-26606c1bfb51) This only happends with legacy version of powershell. Using any theme other than pitch black background theme results in this behaviour. The previous version of windows terminal `1.21.3231.0` does not have this problem.
claunia added the Resolution-By-DesignNeeds-TriageIssue-Bug labels 2026-01-31 08:27:42 +00:00
claunia commented 2026-01-31 08:27:43 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Feb 17, 2025):

We've found some similar issues:

  • #6767 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Feb 17, 2025): We've found some similar issues: - #6767 , similarity score: 81% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:27:44 +00:00
Author
Owner
Copy Link

@canh25xp commented on GitHub (Feb 17, 2025):

This issue seam to happens with older release, it got fixed and then now reappear in this version.

@canh25xp commented on GitHub (Feb 17, 2025): This issue seam to happens with [older release](https://github.com/microsoft/terminal/issues/6767), it got [fixed](https://github.com/microsoft/terminal/pull/6810) and then now reappear in this version.
claunia commented 2026-01-31 08:27:44 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 18, 2025):

@canh25xp I'm afraid the change in color handling is by design. That fix was a temporary hack that has now been removed. The reasoning is explained in PR #17666, but the gist of it is that you need to upgrade PSReadLine, or use a black/white color scheme if that isn't an option.

@j4james commented on GitHub (Feb 18, 2025): @canh25xp I'm afraid the change in color handling is by design. That fix was a temporary hack that has now been removed. The reasoning is explained in PR #17666, but the gist of it is that you need to upgrade PSReadLine, or use a black/white color scheme if that isn't an option.
claunia commented 2026-01-31 08:27:44 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 19, 2025):

Thanks for filing! As j4james said above, this is by design. More info can be found in PR #17666 and the issue it closes. 😊

@carlos-zamora commented on GitHub (Feb 19, 2025): Thanks for filing! As j4james said above, this is by design. More info can be found in PR #17666 and the issue it closes. 😊
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-Triage Resolution-By-Design
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#22932
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?