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

Buttons not rendering correctly when using Ultrawide monitors #18168

New Issue
Closed
opened 2026-01-31 06:05:39 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 06:05:39 +00:00
Owner
Copy Link

Originally created by @ptedeschi on GitHub (Aug 12, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.1826

Other Software

No response

Steps to reproduce

  • Open Terminal in a Ultrawide monitors
  • Open About screen

Expected Behavior

The modal button should display the text "Ok"

Actual Behavior

The modal button only displays a blue rectangle:
image

Originally created by @ptedeschi on GitHub (Aug 12, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.1826 ### Other Software _No response_ ### Steps to reproduce - Open Terminal in a Ultrawide monitors - Open About screen ### Expected Behavior The modal button should display the text "Ok" ### Actual Behavior The modal button only displays a blue rectangle: ![image](https://user-images.githubusercontent.com/6684508/184428335-36f8f10b-b13c-4729-8a72-94104e6c3aeb.png)
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 06:05:39 +00:00
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

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

I'd be shocked if this actually had anything to do with the screen resolution.... Do you have a non-ultrawide monitor that this does/does not repro on/?

What does the color schemes page of the settings UI look like? (There's another bug floating around here this reminds me of)

@zadjii-msft commented on GitHub (Aug 12, 2022): I'd be shocked if this actually had anything to do with the screen resolution.... Do you have a non-ultrawide monitor that this does/does not repro on/? What does the color schemes page of the settings UI look like? (There's another bug floating around here this reminds me of)
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

@ptedeschi commented on GitHub (Aug 16, 2022):

@zadjii-msft The monitor resolution definitely plays a role in this. My setup is a notebook with a resolution of 1920x1080 and an UltraWide monitor 2560x1080 connected to this notebook. When I open the Terminal on the notebook screen, everything is normal. When I open it in Ultrawide monitor, the button has this issue. And I just realized that it's not just the Terminal that gets away with this. The Microsoft Store suffers from the same behavior

@ptedeschi commented on GitHub (Aug 16, 2022): @zadjii-msft The monitor resolution definitely plays a role in this. My setup is a notebook with a resolution of `1920x1080` and an UltraWide monitor `2560x1080` connected to this notebook. When I open the Terminal on the notebook screen, everything is normal. When I open it in Ultrawide monitor, the button has this issue. And I just realized that it's not just the Terminal that gets away with this. The Microsoft Store suffers from the same behavior
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

@J0F3 commented on GitHub (Jan 27, 2023):

I have the same problem. On a monitor with the resolution 5120x1440 the blue buttons do not show the text (like in the screen shot above). But in the internal laptop screen with 3840x2160 every thing is normal.

For me also the background opacity doe not work correctly and is basically unusable on the screen with 5120x1440 resolution:

image
image

I noticed also that it affects not only the Windows Terminal but for example also the Microsoft Store App has show the same issue. So it seems more to be a Window (10?) wide problem that a Windows Terminal specific.

@J0F3 commented on GitHub (Jan 27, 2023): I have the same problem. On a monitor with the resolution 5120x1440 the blue buttons do not show the text (like in the screen shot above). But in the internal laptop screen with 3840x2160 every thing is normal. For me also the background opacity doe not work correctly and is basically unusable on the screen with 5120x1440 resolution: ![image](https://user-images.githubusercontent.com/12759579/215041415-f7f35671-60ed-4860-8d1d-9f00086b13d6.png) ![image](https://user-images.githubusercontent.com/12759579/215041475-58545e92-fe38-4ebe-95d2-15360608ad7a.png) I noticed also that it affects not only the Windows Terminal but for example also the Microsoft Store App has show the same issue. So it seems more to be a Window (10?) wide problem that a Windows Terminal specific.
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 1, 2023):

Hi @J0F3 (or @ptedeschi if you're still seeing this). Circling back around to this. Could you file some feedback using feedback hub? Please file this under Desktop Environment > DWM.

@carlos-zamora commented on GitHub (Mar 1, 2023): Hi @J0F3 (or @ptedeschi if you're still seeing this). Circling back around to this. Could you file some feedback using feedback hub? Please file this under Desktop Environment > DWM.
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 1, 2023):

/feedback

@carlos-zamora commented on GitHub (Mar 1, 2023): /feedback
claunia commented 2026-01-31 06:05:41 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 1, 2023):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@microsoft-github-policy-service[bot] commented on GitHub (Mar 1, 2023): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 06:05:42 +00:00
Author
Owner
Copy Link

@J0F3 commented on GitHub (Mar 15, 2023):

@carlos-zamora Unfortunately I can not use Feedback Hub because it is blocked (company device). But anyway, the issue is gone for me . Since I had connected the device once to a Display Link Docking station the problem was magically gone. So maybe it was more a side effect of the Display Link driver or something...

@J0F3 commented on GitHub (Mar 15, 2023): @carlos-zamora Unfortunately I can not use Feedback Hub because it is blocked (company device). But anyway, the issue is gone for me . Since I had connected the device once to a Display Link Docking station the problem was magically gone. So maybe it was more a side effect of the Display Link driver or something...
claunia commented 2026-01-31 06:05:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 27, 2023):

Hey all, our bot's been acting up the last few weeks. This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. Thanks!

@zadjii-msft commented on GitHub (Mar 27, 2023): Hey all, our bot's been acting up the last few weeks. This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. 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 Issue-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage
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#18168
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?