Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression: Unable to scroll settings with mouse wheel #18410

Closed
fredemmott opened this issue Jan 8, 2025 · 9 comments
Closed

Regression: Unable to scroll settings with mouse wheel #18410

fredemmott opened this issue Jan 8, 2025 · 9 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@fredemmott
Copy link

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
@fredemmott fredemmott added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 8, 2025
Copy link

We've found some similar issues:

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.

@fredemmott fredemmott changed the title Unable to scroll settings with mouse wheel Regression: Unable to scroll settings with mouse wheel Jan 8, 2025
@fredemmott

This comment has been minimized.

@fredemmott

This comment has been minimized.

@fredemmott
Copy link
Author

Worked around by turning on this windows setting: Image

@DHowett
Copy link
Member

DHowett commented 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.

@fredemmott
Copy link
Author

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

@carlos-zamora
Copy link
Member

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: #9340 (comment)

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jan 22, 2025
@fredemmott
Copy link
Author

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

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 23, 2025
@DHowett
Copy link
Member

DHowett commented 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 DHowett closed this as completed Jan 23, 2025
@DHowett DHowett closed this as not planned Won't fix, can't repro, duplicate, stale Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants