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

Top of window border loses color after focus mode/full-screen #13743

New Issue
Closed
opened 2026-01-31 03:50:53 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:50:53 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (May 7, 2021).

Windows Terminal version (or Windows build number)

WindowsTerminal: 1.8.1092.0

Other Software

No response

Steps to reproduce

  1. Enable a keystroke for toggling focus mode; e.g., {"command": "toggleFocusMode", "keys": "shift+f11"},
  2. Enter focus mode (tabs and title hidden)
  3. Go to full-screen (Alt+Enter)
  4. Return from full-screen (Alt+Enter)
  5. Left-click the desktop
  6. Left-click in WT

Expected Behavior

WT's border (accent color) should be intact.

Actual Behavior

After steps 5 and 6, WT has lost the accent color of its top border ...

Normal (magenta-ish accent):
image
After step 5 (window inactive):
image
After step 6 (window active):
image

Originally created by @vefatica on GitHub (May 7, 2021). ### Windows Terminal version (or Windows build number) WindowsTerminal: 1.8.1092.0 ### Other Software _No response_ ### Steps to reproduce 1. Enable a keystroke for toggling focus mode; e.g., {"command": "toggleFocusMode", "keys": "shift+f11"}, 2. Enter focus mode (tabs and title hidden) 3. Go to full-screen (Alt+Enter) 4. Return from full-screen (Alt+Enter) 5. Left-click the desktop 6. Left-click in WT ### Expected Behavior WT's border (accent color) should be intact. ### Actual Behavior After steps 5 and 6, WT has lost the accent color of its top border ... Normal (magenta-ish accent): ![image](https://user-images.githubusercontent.com/61856645/117493415-f51cb880-af40-11eb-9870-a3f40926c255.png) After step 5 (window inactive): ![image](https://user-images.githubusercontent.com/61856645/117493495-0bc30f80-af41-11eb-9a9a-56f2f638ac9c.png) After step 6 (window active): ![image](https://user-images.githubusercontent.com/61856645/117493532-19789500-af41-11eb-8052-b8f9138fd906.png)
claunia commented 2026-01-31 03:50:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 11, 2021):

Meh, I could have sworn there was a dupe for this.

Oh nevermind, the "dupe" was

KNOWN ISSUE: Upon resizing the NCIW, the top frame margin disappears, making that border disappear entirely. 6356aaf has a bunch of WIP work for me trying to fix that, but I couldn't get it quite right.

in #6804.

@zadjii-msft commented on GitHub (May 11, 2021): Meh, I could have sworn there was a dupe for this. Oh nevermind, the "dupe" was > KNOWN ISSUE: Upon resizing the NCIW, the top frame margin disappears, making that border disappear entirely. 6356aaf has a bunch of WIP work for me trying to fix that, but I couldn't get it quite right. in #6804.
claunia commented 2026-01-31 03:50:56 +00:00
Author
Owner
Copy Link

@marbaa commented on GitHub (May 12, 2021):

Windows 10 has few years old bug that top border of any window has different color than the rest of borders. Maybe it is affecting here Terminal as well.

@marbaa commented on GitHub (May 12, 2021): Windows 10 has few years old bug that top border of any window has different color than the rest of borders. Maybe it is affecting here Terminal as well.
claunia commented 2026-01-31 03:50:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 18, 2021):

You know what, this might just be one of those things that's "fixed in Windows 11". I can't get this to repro any longer - I'm guessing with all the DWM work they've done, they fixed the root cause.

It'd be neigh impossible to track down which change was the individual one that did it, and I'd reckon it'd be similarly impossible for us to backport the fix to win10, considering the breadth of DWM changes.

@zadjii-msft commented on GitHub (Aug 18, 2021): You know what, this might just be one of those things that's "fixed in Windows 11". I can't get this to repro any longer - I'm guessing with all the DWM work they've done, they fixed the root cause. It'd be neigh impossible to track down which change was the individual one that did it, and I'd reckon it'd be similarly impossible for us to backport the fix to win10, considering the breadth of DWM changes.
claunia commented 2026-01-31 03:50:57 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jan 4, 2022):

I can no longer reproduce it using

Microsoft Windows 10 Pro for Workstations
10.0.19044.1415 (2009, 21H2)
Windows Terminal Preview 1.12.3472.0

@vefatica commented on GitHub (Jan 4, 2022): I can no longer reproduce it using Microsoft Windows 10 Pro for Workstations 10.0.19044.1415 (2009, 21H2) Windows Terminal Preview 1.12.3472.0
claunia commented 2026-01-31 03:50:57 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jan 4, 2022):

And I CAN reproduce it with

Microsoft Windows 10 Pro for Workstations
10.0.19044.1415 (2009, 21H2)
Windows Terminal 1.11.3471.0

@vefatica commented on GitHub (Jan 4, 2022): And I CAN reproduce it with Microsoft Windows 10 Pro for Workstations 10.0.19044.1415 (2009, 21H2) Windows Terminal 1.11.3471.0
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-UserInterface Issue-Bug Priority-3 Product-Terminal Resolution-Fix-Available
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#13743
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?