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

Command Prompt text becomes black when scrolling #1087

New Issue
Closed
opened 2026-01-30 22:16:08 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:16:08 +00:00
Owner
Copy Link

Originally created by @miniksa on GitHub (May 14, 2019).

Ported from customer feedback bug MSFT:21393297.

I haven't reproduced or investigated this yet.

  1. use command prompt enough to get multiple pages of text
  2. scroll up to previous text
    when scrolling up, some of the text will become black, making it unreadable. Scrolling back down may or may not bring it back. Highlighting the black space shows the text exists and will bring it back to white on black.
Originally created by @miniksa on GitHub (May 14, 2019). Ported from customer feedback bug MSFT:21393297. I haven't reproduced or investigated this yet. > 1. use command prompt enough to get multiple pages of text > 2. scroll up to previous text > when scrolling up, some of the text will become black, making it unreadable. Scrolling back down may or may not bring it back. Highlighting the black space shows the text exists and will bring it back to white on black.
claunia commented 2026-01-30 22:16:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 16, 2022):

Hey so we ported this out of the OS issue tracker like, 3 years ago. It was specifically referencing the vintage console window, not the Terminal window. That being said, we haven't gotten more reports of this for the console since then. There also wasn't more info in the original issue (internally) which we could really use to investigate.

I'm inclined to close this out. Niksa can veto if he wants.

@zadjii-msft commented on GitHub (Aug 16, 2022): Hey so we ported this out of the OS issue tracker like, 3 years ago. It was specifically referencing the vintage console window, not the Terminal window. That being said, we haven't gotten more reports of this for the _console_ since then. There also wasn't more info in the original issue (internally) which we could really use to investigate. I'm inclined to close this out. Niksa can veto if he wants.
claunia commented 2026-01-30 22:16:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 20, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 20, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 22:16:10 +00:00
Author
Owner
Copy Link

@nbstrong commented on GitHub (Aug 24, 2022):

Be awesome if this could be re-opened.

I am also getting this issue with Windows Terminal when running command prompt.

Specifically I have 999999 history size. I am outputting a ton of data from a python script to the terminal screen. When the script is done if I try to scroll up to view the data, the terminal window goes black.

If I hit enter, the data re-appears but I cannot scroll up.

@nbstrong commented on GitHub (Aug 24, 2022): Be awesome if this could be re-opened. I am also getting this issue with Windows Terminal when running command prompt. Specifically I have 999999 history size. I am outputting a ton of data from a python script to the terminal screen. When the script is done if I try to scroll up to view the data, the terminal window goes black. If I hit enter, the data re-appears but I cannot scroll up.
claunia commented 2026-01-30 22:16:11 +00:00
Author
Owner
Copy Link

@nbstrong commented on GitHub (Aug 24, 2022):

Furthermore, CLS to clear the screen crashes Windows Terminal.

Happy to provide anything needed.

@nbstrong commented on GitHub (Aug 24, 2022): Furthermore, CLS to clear the screen crashes Windows Terminal. Happy to provide anything needed.
claunia commented 2026-01-30 22:16:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2022):

@nbstrong Can you file a new issue actually? This one was ported from an internal database like, years ago, and ultimately probably has a different root cause. There's a couple other threads that sound familiar on the repo, #13499 comes to mind.

A screen recording might also be helpful here.

Thanks!

@zadjii-msft commented on GitHub (Aug 24, 2022): @nbstrong Can you file a new issue actually? This one was ported from an internal database like, years ago, and ultimately probably has a different root cause. There's a couple other threads that sound familiar on the repo, #13499 comes to mind. A screen recording might also be helpful here. Thanks!
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-Rendering Issue-Bug Needs-Author-Feedback Needs-Repro Product-Conhost
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#1087
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?