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

Thin white line or thin blue line at the bottom of the screen on Windows 11 when clicking on the Maximize button #15499

New Issue
Open
opened 2026-01-31 04:40:24 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:40:24 +00:00
Owner
Copy Link

Originally created by @csdvrx on GitHub (Oct 10, 2021).

Windows Terminal version (or Windows build number)

1.10.2714.0 to 1.11.2731.0 (both Windows Terminal and Windows Terminal Preview)

Other Software

default Windows 11 installation with WSL2

Steps to reproduce

Start 2 terminals, put one slightly over the other: there is no white line as can be seen here on the corner

image

Click on the maximize button, the taskbar is present at the bottom, which is something someone using a maximized terminal may not want, given the strong contrast and eye strain it creates (a terminal with black background and white text with a white taskbar at the bottom and a white titlebar on top)

The next logical step for this user is to attempt a basic configuration, simply using the available menu options that are shown or known to this user: in Windows Terminal, select the dark theme, and in settings, configure the taskbar to auto hide.

image

image

However, this results in a thin line at the bottom:

image

Expected Behavior

Pressing on maximize should maximize the window, and never leave any thin line at the bottom, regardless of the thin line color: this can be a issue with OLED displays, where the screen may get a "burn in" of any persistent element, like this thin line.

If a thin line must be left for impervious reasons (ex: as a visual reminder), the thin line color should be configurable by the user, to match the theme or to be less distracting.

Alternatively, if a strong visual reminder of the taskbar must always be left in fullscreen mode, there should be another mode grossly equivalent to "full screen" mode, maybe called differently to avoid confusion with the default fullscreen mode, but offering the option to have no thin lines at the bottom (something irrelevant with the current workflow), while still offering the list of tabs opened (something highly relevant with the current workflow).

Actual Behavior

After these 2 settings, there is now a thin white line at the bottom. Unless reverting the taskbar autohide, any further setting will only make the situation worse.

For example, the user may at this point attempt configuring shortcuts (a more advanced approach, but desperate times call for desperate moves...), where the only 2 choices available (focus mode and fullscreen mode) will not work:

  • focus mode will remove the tabs and the title bar (which the user may want to keep, as it's not the theme consistent titlebar that's breaking the focus, but the thin line!)
  • fullscreen mode will also leave a thin line, except this time it will be a thin blue line:

image

It may not be easily visible outside fullscreen mode, but you can download the image and show it in Paint/fullscreen if you want check the bottom for the precise color:
image

image

This behavior of fullscreen mode is possibly due to how DWM works with full screen applications when the taskbar is set to autohide, as there is no such thin line when the titlebar is not set to autohide and using the same shortcut and Terminal configuation.

However, this DWM behavior means there is no way to:

  • keep the default Windows theme system wide ("light", with a whitish background)
  • while also using Terminal default theme ("dark", with a black background)
  • without either introducing visual inconsistencies (whitish elements on the top and bottom of the screen) or sacrificing the titlebar and tabs (the list of tabs being extremely useful when several remote sessions are opened, far more than a visual reminder the taskbar still exist, as it can be easily brought back when pressing the windows key)

Even worse: users who followed a "reasonable escalation" approach will be left with the worst of both worlds, with no tabs in fullscreen mode, yet the thin blue line due to setting the titlebar to autohide - a thin blue line that wouldn't be present otherwise!

Maybe there should be a "third mode" that would:

  • maximize the Terminal
  • while preserving the display of Terminal tabs (important for the work flow!)
  • while preventing other clutter/visual inconsistencies not important for the work flow (ex: thin lines at the bottom), or at least offering the user to fully control them

A reasonable setting would be to at least let the user control the color of the thin blue line acting as a visual reminder there is a taskbar: a better color could be configured, matching the background if necessary, whether dark (for OLED) or light (for eInk).

While colors identical to the background color may be considered "less readable" and therefore less favorable settings, user preferences should be allowed to override such concerns, for example in these specific situation due to the display technology used.

Regardless of the root causes (DWM?), some users may also object to displaying a mandatory "thin blue line" on their display, for political reasons: a bing search on "thin blue line" reveals the connotation with law enforcement in North America, and a newer but potentially more problematic political connotations as noted in wikipedia ('The "thin blue line" has also been associated with white nationalists in the US, particularly after the Unite the Right rally in 2017.[7][8]')

This issue may be related to #4837, #3064 or #3425 which was closed because "this is the issue for terminal has white borders in dark mode, which is 100% fixed. If you want to discuss changing the default for light mode, please file a separate issue"

It may have been short-sighted to ignore the separate issue for light mode, as light mode is now the default Windows-11 theme.

Originally created by @csdvrx on GitHub (Oct 10, 2021). ### Windows Terminal version (or Windows build number) 1.10.2714.0 to 1.11.2731.0 (both Windows Terminal and Windows Terminal Preview) ### Other Software default Windows 11 installation with WSL2 ### Steps to reproduce Start 2 terminals, put one slightly over the other: there is no white line as can be seen here on the corner ![image](https://user-images.githubusercontent.com/49044530/136706739-ee8531e5-c62d-450f-b65a-b3667e1168cc.png) Click on the maximize button, the taskbar is present at the bottom, which is something someone using a maximized terminal may not want, given the strong contrast and eye strain it creates (a terminal with black background and white text with a white taskbar at the bottom and a white titlebar on top) The next logical step for this user is to attempt a basic configuration, simply using the available menu options that are shown or known to this user: in Windows Terminal, select the dark theme, and in settings, configure the taskbar to auto hide. ![image](https://user-images.githubusercontent.com/49044530/136707152-a0801d56-0480-4323-b5b9-2395c818e572.png) ![image](https://user-images.githubusercontent.com/49044530/136707162-491f7fbc-eeb2-4387-a519-2cfbdf09b17e.png) However, this results in a thin line at the bottom: ![image](https://user-images.githubusercontent.com/49044530/136707238-d086c32c-627b-4e0d-b881-797b7270c118.png) ### Expected Behavior Pressing on maximize should maximize the window, and never leave any thin line at the bottom, regardless of the thin line color: this can be a issue with OLED displays, where the screen may get a "burn in" of any persistent element, like this thin line. If a thin line must be left for impervious reasons (ex: as a visual reminder), the thin line color should be configurable by the user, to match the theme or to be less distracting. Alternatively, if a strong visual reminder of the taskbar must always be left in fullscreen mode, there should be another mode grossly equivalent to "full screen" mode, maybe called differently to avoid confusion with the default fullscreen mode, but offering the option to have no thin lines at the bottom (something irrelevant with the current workflow), while still offering the list of tabs opened (something highly relevant with the current workflow). ### Actual Behavior After these 2 settings, there is now a thin white line at the bottom. Unless reverting the taskbar autohide, any further setting will only make the situation worse. For example, the user may at this point attempt configuring shortcuts (a more advanced approach, but desperate times call for desperate moves...), where the only 2 choices available (focus mode and fullscreen mode) will not work: - focus mode will remove the tabs and the title bar (which the user may want to keep, as it's not the theme consistent titlebar that's breaking the focus, but the thin line!) - fullscreen mode will also leave a thin line, except this time it will be a thin blue line: ![image](https://user-images.githubusercontent.com/49044530/136707344-95da7c0d-8794-4eba-8027-d3145a6cf7ee.png) It may not be easily visible outside fullscreen mode, but you can download the image and show it in Paint/fullscreen if you want check the bottom for the precise color: ![image](https://user-images.githubusercontent.com/49044530/136708359-fa74f12b-e997-4348-88fb-27b6b35e4b6e.png) ![image](https://user-images.githubusercontent.com/49044530/136708503-2d26343f-9738-4284-adbb-295abbe678d5.png) This behavior of fullscreen mode is possibly due to how DWM works with full screen applications when the taskbar is set to autohide, as there is no such thin line when the titlebar is not set to autohide and using the same shortcut and Terminal configuation. However, this DWM behavior means there is no way to: - keep the default Windows theme system wide ("light", with a whitish background) - while also using Terminal default theme ("dark", with a black background) - without either introducing visual inconsistencies (whitish elements on the top and bottom of the screen) or sacrificing the titlebar and tabs (the list of tabs being extremely useful when several remote sessions are opened, far more than a visual reminder the taskbar still exist, as it can be easily brought back when pressing the windows key) Even worse: users who followed a "reasonable escalation" approach will be left with the worst of both worlds, with no tabs in fullscreen mode, yet the thin blue line due to setting the titlebar to autohide - a thin blue line that wouldn't be present otherwise! Maybe there should be a "third mode" that would: - maximize the Terminal - while preserving the display of Terminal tabs (important for the work flow!) - while preventing other clutter/visual inconsistencies not important for the work flow (ex: thin lines at the bottom), or at least offering the user to fully control them A reasonable setting would be to at least let the user control the color of the thin blue line acting as a visual reminder there is a taskbar: a better color could be configured, matching the background if necessary, whether dark (for OLED) or light (for eInk). While colors identical to the background color may be considered "less readable" and therefore less favorable settings, user preferences should be allowed to override such concerns, for example in these specific situation due to the display technology used. Regardless of the root causes (DWM?), some users may also object to displaying a mandatory "thin blue line" on their display, for political reasons: a bing search on "thin blue line" reveals the connotation with law enforcement in North America, and a newer but potentially more problematic political connotations as noted in wikipedia ('The "thin blue line" has also been associated with white nationalists in the US, particularly after the Unite the Right rally in 2017.[7][8]') This issue may be related to #4837, #3064 or #3425 which was closed because "this is the issue for terminal has white borders in dark mode, which is 100% fixed. If you want to discuss changing the default for light mode, please file a separate issue" It may have been short-sighted to ignore the separate issue for light mode, as light mode is now the default Windows-11 theme.
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-Question Needs-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Answered
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#15499
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?