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

The titlebar is visible when using vintage opacity with a HIGH DPI display #15388

New Issue
Closed
opened 2026-01-31 04:37:08 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:37:08 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Sep 29, 2021).

Originally assigned to: @carlos-zamora on GitHub.

discovered in the 1.12 bug bash on 9/28

image

regressed in #11180

Originally created by @zadjii-msft on GitHub (Sep 29, 2021). Originally assigned to: @carlos-zamora on GitHub. _discovered in the 1.12 bug bash on 9/28_ ![image](https://user-images.githubusercontent.com/18356694/135273925-4fea4eb4-d3b0-40df-943d-f7988ead0d10.png) regressed in #11180
claunia commented 2026-01-31 04:37:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2021):

I could not for the life of me get a repro, but @carlos-zamora has one, so he gets the cookie. I'm guessing this has to do with the changes to IslandWindow / NonClientIslandWindow in #11180. I'd start there. I'm guessing the titlebar isn't getting scaled right for the DPI, or at least the MARGINS we're passing to DwnExtendFrameIntoClientArea aren't scaled right? hard to say.

@zadjii-msft commented on GitHub (Sep 29, 2021): I could not for the life of me get a repro, but @carlos-zamora has one, so he gets the cookie. I'm guessing this has to do with the changes to `IslandWindow` / `NonClientIslandWindow` in #11180. I'd start there. I'm guessing the titlebar isn't getting scaled right for the DPI, or at least the MARGINS we're passing to `DwnExtendFrameIntoClientArea` aren't scaled right? hard to say.
claunia commented 2026-01-31 04:37:10 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Sep 30, 2021):

Ok. I did a bit of digging. Found a few interesting notes:

  • it doesn't happen when initialPosition is set to the non-high DPI monitor
  • it seems to particularly occur when the window is dragged from a high DPI to a non-high DPI monitor

Looking for the code where we refresh the window size on that drag. Surprisingly, NonClientIslandWindow::_UpdateFrameMargins isn't called when that happens.

@carlos-zamora commented on GitHub (Sep 30, 2021): Ok. I did a bit of digging. Found a few interesting notes: - it doesn't happen when `initialPosition` is set to the non-high DPI monitor - it seems to particularly occur when the window is dragged from a high DPI to a non-high DPI monitor Looking for the code where we refresh the window size on that drag. Surprisingly, `NonClientIslandWindow::_UpdateFrameMargins` isn't called when that happens.
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-Windowing Issue-Bug Needs-Repro Needs-Triage Priority-3 Product-Terminal Resolution-Fix-Committed Severity-Blocking
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#15388
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?