Regression: Unable to scroll settings with mouse wheel #22747

Closed
opened 2026-01-31 08:22:15 +00:00 by claunia · 9 comments
Owner

Originally created by @fredemmott on GitHub (Jan 8, 2025).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.22631.4602

Other Software

No response

Steps to reproduce

  1. Open settings
  2. Go to a page with a scroll bar, such as 'Profiles' -> 'defaults' -> 'appearance'
  3. Attempt to scroll with scroll wheel

Expected Behavior

Settings list scrolls

Actual Behavior

Either:

  • nothing
  • if 'appearance' is open, sometimes the scroll wheel changes the color scheme, even if the color scheme combo box has never been focussed, and even if the mouse is over it
Originally created by @fredemmott on GitHub (Jan 8, 2025). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.22631.4602 ### Other Software _No response_ ### Steps to reproduce 1. Open settings 2. Go to a page with a scroll bar, such as 'Profiles' -> 'defaults' -> 'appearance' 3. Attempt to scroll with scroll wheel ### Expected Behavior Settings list scrolls ### Actual Behavior Either: - nothing - if 'appearance' is open, sometimes the scroll wheel changes the color scheme, even if the color scheme combo box has never been focussed, and even if the mouse is over it
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:22:15 +00:00
Author
Owner

@similar-issues-ai[bot] commented on GitHub (Jan 8, 2025):

We've found some similar issues:

  • #12352 , similarity score: 84%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Jan 8, 2025): We've found some similar issues: - #12352 , similarity score: 84% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
Author
Owner

@fredemmott commented on GitHub (Jan 8, 2025):

It is a similar one, but it is a new regression; Most likely it is the regression introduced in WinUI3 v1.6, which also affects all other WinUI3 apps, including the WinUI 3 Gallery - however my report there has essentially been closed as 'works on my machine'.

https://github.com/microsoft/microsoft-ui-xaml/issues/9979

@fredemmott commented on GitHub (Jan 8, 2025): It is a similar one, but it is a new regression; Most likely it is the regression introduced in WinUI3 v1.6, which also affects all other WinUI3 apps, including the WinUI 3 Gallery - however my report there has essentially been closed as 'works on my machine'. https://github.com/microsoft/microsoft-ui-xaml/issues/9979
Author
Owner

@fredemmott commented on GitHub (Jan 8, 2025):

Interestingly, scrolling in actual terminal tabs works fine - it's just the settings page. It looks like the terminal tabs have their own WM_MOUSEWHEEL handing here, rather than depending on WinUI3: src/terminal/input/mouseInput.cpp

@fredemmott commented on GitHub (Jan 8, 2025): Interestingly, scrolling in actual terminal tabs works fine - it's just the settings page. It looks like the terminal tabs have their own WM_MOUSEWHEEL handing here, rather than depending on WinUI3: [src/terminal/input/mouseInput.cpp](https://github.com/microsoft/terminal/blob/b25fe55e94197be667625acef00506ef1636d137/src/terminal/input/mouseInput.cpp#L35)
Author
Owner

@fredemmott commented on GitHub (Jan 8, 2025):

Worked around by turning on this windows setting: Image

@fredemmott commented on GitHub (Jan 8, 2025): Worked around by turning on this windows setting: <img width="1015" alt="Image" src="https://github.com/user-attachments/assets/38c77213-1d10-43a0-a4ef-0290d061795e" />
Author
Owner

@DHowett commented on GitHub (Jan 8, 2025):

Most likely it is the regression introduced in WinUI3 v1.6

Unfortunately, the trick here is that Terminal is not using WinUI 3. The only version of WinUI we use is the one that comes with the OS.

@DHowett commented on GitHub (Jan 8, 2025): > Most likely it is the regression introduced in WinUI3 v1.6 Unfortunately, the trick here is that Terminal is not using WinUI 3. The only version of WinUI we use is the one that comes with the OS.
Author
Owner

@fredemmott commented on GitHub (Jan 8, 2025):

Sorry for the misleading comments then :) Interesting that the same workaround works

@fredemmott commented on GitHub (Jan 8, 2025): Sorry for the misleading comments then :) Interesting that the same workaround works
Author
Owner

@carlos-zamora commented on GitHub (Jan 22, 2025):

Thanks for filing! Sounds like this may be a duplicate of #9340. Mind taking a look through the thread and seeing if it helps /? Looks like this was a proposed solution: https://github.com/microsoft/terminal/issues/9340#issuecomment-885822956

@carlos-zamora commented on GitHub (Jan 22, 2025): Thanks for filing! Sounds like this may be a duplicate of #9340. Mind taking a look through the thread and seeing if it helps /? Looks like this was a proposed solution: https://github.com/microsoft/terminal/issues/9340#issuecomment-885822956
Author
Owner

@fredemmott commented on GitHub (Jan 23, 2025):

I don't use that third party app, and can reproduce this on a clean Vm.

@fredemmott commented on GitHub (Jan 23, 2025): I don't use that third party app, and can reproduce this on a clean Vm.
Author
Owner

@DHowett commented on GitHub (Jan 23, 2025):

I'm sorry, I think we got our wires crossed. This is a Windows platform limitation due to how WinUI 2 hosts XAML content in Win32 applications. It should reproduce in the roughly one other application ("perception simulation input", lives in system32) that uses WinUI 2 Islands. It looks like Facebook authored a workaround for this issue in React Native, but we're not likely to take it here in Terminal.

The nitty gritty is that the input site XAML uses to collect input is neither focused nor active when the Terminal window is.

@DHowett commented on GitHub (Jan 23, 2025): I'm sorry, I think we got our wires crossed. _This_ is a Windows platform limitation due to how WinUI _2_ hosts XAML content in Win32 applications. It should reproduce in the roughly one other application ("perception simulation input", lives in system32) that uses WinUI 2 Islands. It looks like Facebook authored a workaround for this issue in React Native, but we're not likely to take it here in Terminal. The nitty gritty is that the input site XAML uses to collect input is neither focused nor active when the Terminal window is.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22747