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

Menu bar interaction points clicks do not work on 3440x1440 resolution #9886

New Issue
Closed
opened 2026-01-31 02:06:38 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:06:38 +00:00
Owner
Copy Link

Originally created by @seangwright on GitHub (Jul 28, 2020).

Environment

Windows build number: [run [Environment]::OSVersion for powershell, or ver for cmd]

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal version (if applicable): Version: 1.1.2021.0

Any other software?
posh-git, oh-my-posh, PowerToys 0.19.2

Displays:

  1. 3440x1440, 100% scaling
  2. 1920x1080, 100% scaling

Steps to reproduce

Open Windows Terminal on a 3440x1440 resolution display
Try to use any of the interaction points on the top Terminal bar (new tab, options, minimize, maximize, close)

Expected behavior

Interactions work

Actual behavior

Interactions do not respond to mouse clicks

windows-terminal-resolution-issue

(yellow bubbles signify clicks)

Notes

When I move the Terminal to my 1920x1080 display, everything works as expected. When I move it back to my 3440x1440 display, the menu interaction points do not work.

Originally created by @seangwright on GitHub (Jul 28, 2020). # Environment Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 ``` Windows Terminal version (if applicable): Version: 1.1.2021.0 Any other software? posh-git, oh-my-posh, PowerToys 0.19.2 Displays: 1) 3440x1440, 100% scaling 2) 1920x1080, 100% scaling # Steps to reproduce Open Windows Terminal on a 3440x1440 resolution display Try to use any of the interaction points on the top Terminal bar (new tab, options, minimize, maximize, close) # Expected behavior Interactions work # Actual behavior Interactions do not respond to mouse clicks ![windows-terminal-resolution-issue](https://user-images.githubusercontent.com/1382768/88614650-2edd9c00-d05e-11ea-8282-5faae4f6073a.gif) (yellow bubbles signify clicks) # Notes When I move the Terminal to my 1920x1080 display, everything works as expected. When I move it back to my 3440x1440 display, the menu interaction points do not work.
claunia added the Area-InputResolution-DuplicateProduct-Terminal labels 2026-01-31 02:06:39 +00:00
claunia commented 2026-01-31 02:06:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 28, 2020):

Are you using PowerToys, or do you have it running in the background?

@DHowett commented on GitHub (Jul 28, 2020): Are you using PowerToys, or do you have it running in the background?
claunia commented 2026-01-31 02:06:40 +00:00
Author
Owner
Copy Link

@seangwright commented on GitHub (Jul 28, 2020):

Yup, I'm using PowerToys 0.19.2, and it is running currently.

@seangwright commented on GitHub (Jul 28, 2020): Yup, I'm using PowerToys 0.19.2, and it is running currently.
claunia commented 2026-01-31 02:06:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 28, 2020):

If you exit it, does mouse input start working again?

@DHowett commented on GitHub (Jul 28, 2020): If you exit it, does mouse input start working again?
claunia commented 2026-01-31 02:06:40 +00:00
Author
Owner
Copy Link

@seangwright commented on GitHub (Jul 28, 2020):

@DHowett Yup, closing PowerToys immediately made the bar interactive again and I could add new tabs/close ect...

It's weird - I'm noticing that sometimes there isn't an issue and sometimes there is, but the issue, when it does appear, is always on my 3440x1440 display.

@seangwright commented on GitHub (Jul 28, 2020): @DHowett Yup, closing PowerToys immediately made the bar interactive again and I could add new tabs/close ect... It's weird - I'm noticing that sometimes there isn't an issue and sometimes there is, but the issue, when it does appear, is always on my 3440x1440 display.
claunia commented 2026-01-31 02:06:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 29, 2020):

Thanks for following up! I'm gonna mark this as a dup of #6120 since they seem to have the same root cause.

/dup #6120

@zadjii-msft commented on GitHub (Jul 29, 2020): Thanks for following up! I'm gonna mark this as a dup of #6120 since they seem to have the same root cause. /dup #6120
claunia commented 2026-01-31 02:06:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 29, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 29, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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-Input Product-Terminal Resolution-Duplicate
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#9886
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?