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

Incorrect background color when scrolling up #185

New Issue
Closed
opened 2026-01-30 21:44:55 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 21:44:55 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Mar 8, 2018).

Originally assigned to: @zadjii-msft on GitHub.

Windows build number: [Version 10.0.16299.248]

If I use an ANSI sequence to set the background color attribute, then move to the bottom of the screen and output some newlines so the screen scrolls up, I'd expect the newly revealed lines to have the background color that I just set.

Similarly, if I move to the top of the screen, and output the reverse feed sequence (\033M) so the screen scrolls down, I'd again expect the new revealed lines to use the current background color.

The later case (scrolling down) works as expected, but scrolling up does not.

Test case (from a bash shell):
printf "\033[44m\033[200B\n\n\033[200A\033M\033[m"

I'd expect the above sequence to result in both the top and bottom lines of the screen having a blue background (which is what I see in a Linux console), but in the Windows 10 console, only the top line is blue.

Note that the scroll up sequence (\033[S) has similar problems, although it's a little more complicated. The first line that's revealed when scrolling up will have the wrong background color, but subsequent lines will be correct. Scrolling down (like reverse feed) always seems to work as expected.

I suspect this may be related to issue #70. I apologise if it's just a duplicate.

Originally created by @j4james on GitHub (Mar 8, 2018). Originally assigned to: @zadjii-msft on GitHub. **Windows build number:** [Version 10.0.16299.248] If I use an ANSI sequence to set the background color attribute, then move to the bottom of the screen and output some newlines so the screen scrolls up, I'd expect the newly revealed lines to have the background color that I just set. Similarly, if I move to the top of the screen, and output the reverse feed sequence (`\033M`) so the screen scrolls down, I'd again expect the new revealed lines to use the current background color. The later case (scrolling down) works as expected, but scrolling up does not. **Test case (from a bash shell):** `printf "\033[44m\033[200B\n\n\033[200A\033M\033[m"` I'd expect the above sequence to result in both the top and bottom lines of the screen having a blue background (which is what I see in a Linux console), but in the Windows 10 console, only the top line is blue. Note that the scroll up sequence (`\033[S`) has similar problems, although it's a little more complicated. The first line that's revealed when scrolling up will have the wrong background color, but subsequent lines will be correct. Scrolling down (like reverse feed) always seems to work as expected. I suspect this may be related to issue #70. I apologise if it's just a duplicate.
claunia added the Product-ConhostWork-Item labels 2026-01-30 21:44:55 +00:00
claunia commented 2026-01-30 21:44:56 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (May 4, 2018):

Thanks for filing. I can confirm that Console with Ubuntu/WSL does this:
image

Whereas an Ubuntu VM does this:
image

@bitcrazed commented on GitHub (May 4, 2018): Thanks for filing. I can confirm that Console with Ubuntu/WSL does this: ![image](https://user-images.githubusercontent.com/961950/39609818-90513636-4f00-11e8-86ba-ddfea65ebc53.png) Whereas an Ubuntu VM does this: ![image](https://user-images.githubusercontent.com/961950/39609833-b387e2f8-4f00-11e8-8c43-84fd8253fc9a.png)
claunia commented 2026-01-30 21:44:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 8, 2018):

I love when bug reports have a nice simple string of VT sequences like this. Makes it really easy to debug and find solutions.

Submitting the PR now, shouldn't be too hard to get through code review.

@zadjii-msft commented on GitHub (Jun 8, 2018): I love when bug reports have a nice simple string of VT sequences like this. Makes it really easy to debug and find solutions. Submitting the PR now, shouldn't be too hard to get through code review.
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 Product-Conhost Work-Item
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#185
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?