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

Can't scroll or drag files over some areas with non 100% scaling #3659

New Issue
Closed
opened 2026-01-30 23:26:40 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 23:26:40 +00:00
Owner
Copy Link

Originally created by @dsafa on GitHub (Aug 29, 2019).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): built from master @ f4294b1

Any other software? N/A

Steps to reproduce

  1. Turn off the Windows setting scroll inactive window when I hover over them
  2. Have terminal on monitor with scaling other than 100%
  3. Have enough text to scroll
  4. Focus terminal and scroll with mouse wheel

Expected behavior

Terminal should scroll

Actual behavior

Scrolling behavior is different depending on the mouse position. In some areas, it scrolls properly. In other regions, scrolling won't work.

  • If scaling is 100%, then scrolling works properly. If scroll inactive window setting is on, then scrolling works properly.
  • Same issue for both normal and non client window

scroll-region

Heres what I think is happening:

With scroll inactive window off, the wm_mousewheel messages are only be sent to current focused window (If i've read the docs correctly).
I think that the window that takes focus is not scaled properly so in some areas the mouse is 'outside' and won't receive the mouse wheel messages (maybe it needs to be focused and hovered?).
Terminal does have a couple windows (the host and the xaml island ones) but i'm not sure which one takes focus when terminal is active. I tried checking for wm_mousewheel in the window procs but I could not see the message being sent.
I have my suspicions that it's the top level window that is supposed to be receiving the messages because using Spy++, when I highlighted the top level window, its size also matched the area where scrolling works. But visually, everything seems to be scaled properly so I'm not too sure now.

Originally created by @dsafa on GitHub (Aug 29, 2019). # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): built from master @ f4294b1 Any other software? N/A ``` # Steps to reproduce 1. Turn off the Windows setting `scroll inactive window when I hover over them` 2. Have terminal on monitor with scaling other than 100% 3. Have enough text to scroll 4. Focus terminal and scroll with mouse wheel # Expected behavior Terminal should scroll # Actual behavior Scrolling behavior is different depending on the mouse position. In some areas, it scrolls properly. In other regions, scrolling won't work. - If scaling is 100%, then scrolling works properly. If scroll inactive window setting is on, then scrolling works properly. - Same issue for both normal and non client window ![scroll-region](https://user-images.githubusercontent.com/7334282/63960813-28a50100-ca44-11e9-86f2-c50a889501bc.png) Heres what I think is happening: With `scroll inactive window` off, the wm_mousewheel messages are only be sent to current focused window (If i've read the docs correctly). I think that the window that takes focus is not scaled properly so in some areas the mouse is 'outside' and won't receive the mouse wheel messages (maybe it needs to be focused and hovered?). Terminal does have a couple windows (the host and the xaml island ones) but i'm not sure which one takes focus when terminal is active. I tried checking for wm_mousewheel in the window procs but I could not see the message being sent. I have my suspicions that it's the top level window that is supposed to be receiving the messages because using Spy++, when I highlighted the top level window, its size also matched the area where scrolling works. But visually, everything seems to be scaled properly so I'm not too sure now.
claunia commented 2026-01-30 23:26:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 29, 2019):

@austin-lamb & @ocalvo might be interested in this

@zadjii-msft commented on GitHub (Aug 29, 2019): @austin-lamb & @ocalvo might be interested in this
claunia commented 2026-01-30 23:26:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 29, 2019):

I just want to say we all really appreciate how robust this bug report is and how well you've investigated it.
Thanks!

@DHowett-MSFT commented on GitHub (Aug 29, 2019): I just want to say we all really appreciate how robust this bug report is and how well you've investigated it. Thanks!
claunia commented 2026-01-30 23:26:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 11, 2020):

Oh no, this is likely a platform bug. We've got a discussion with some folks on the XAML team to help investigate this, but I think this isn't going to make the 1.0 cut.

This issue is now tracking the internal bugs MSFT:25518888 and MSFT:23625486, and the external https://github.com/microsoft/microsoft-ui-xaml/issues/2101

@zadjii-msft commented on GitHub (Mar 11, 2020): Oh no, this is likely a platform bug. We've got a discussion with some folks on the XAML team to help investigate this, but I think this isn't going to make the 1.0 cut. This issue is now tracking the internal bugs MSFT:25518888 and MSFT:23625486, and the external https://github.com/microsoft/microsoft-ui-xaml/issues/2101
claunia commented 2026-01-30 23:26:42 +00:00
Author
Owner
Copy Link

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

Also adding MSFT:35026617 to the list of internal tracking issues, since 23625486 was resolved, but didn't fix this.

@zadjii-msft commented on GitHub (Aug 3, 2021): Also adding MSFT:35026617 to the list of internal tracking issues, since 23625486 was resolved, but didn't fix this.
claunia commented 2026-01-30 23:26:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 11, 2022):

Alrighty so MSFT:35026617 was fixed earlier this year, but unfortunately doesn't make the cut to service back to Windows 10. Alas 🤷. Anyways, this is fixed on the latest Windows 11 builds, so I'm gonna close this out, since there's nothing else for us to do here. Thanks!

@zadjii-msft commented on GitHub (Apr 11, 2022): Alrighty so MSFT:35026617 was fixed earlier this year, but unfortunately doesn't make the cut to service back to Windows 10. Alas 🤷. Anyways, this is fixed on the latest Windows 11 builds, so I'm gonna close this out, since there's nothing else for us to do here. Thanks!
claunia commented 2026-01-30 23:26:42 +00:00
Author
Owner
Copy Link

@malcolm-bell commented on GitHub (Nov 16, 2023):

Still not working.
Windows Terminal
Version: 1.18.2822.0
Windows 11 22H2 OS build 22621.2428

https://github.com/microsoft/terminal/assets/104540921/6dd0b1e4-2d9e-4c1e-83fd-6e5d91e9e604

@malcolm-bell commented on GitHub (Nov 16, 2023): Still not working. Windows Terminal Version: 1.18.2822.0 Windows 11 22H2 OS build 22621.2428 https://github.com/microsoft/terminal/assets/104540921/6dd0b1e4-2d9e-4c1e-83fd-6e5d91e9e604
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 Needs-Tag-Fix Priority-3 Product-Terminal Tracking-External
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#3659
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?