Scroll wheel does not work in settings UI #12811

@zadjii-msft commented on GitHub (Mar 2, 2021):

oh my gosh is this that weird trackpad bug? Lemme try finding that in the history.

@otaconjh What mouse are you using to scroll the Terminal? Is it by any chance a synaptics trackpad?

EDIT: My theory is that this is a variation on #979, #2606 and microsoft/microsoft-ui-xaml#2101

@zadjii-msft commented on GitHub (Mar 2, 2021): oh my gosh is this that weird trackpad bug? Lemme try finding that in the history. @otaconjh What mouse are you using to scroll the Terminal? Is it by any chance a synaptics trackpad? EDIT: My theory is that this is a variation on #979, #2606 and microsoft/microsoft-ui-xaml#2101

claunia commented

@ghost commented on GitHub (Mar 3, 2021):

It occurred on my work laptop but I was using a bluetooth mouse. 'HID-compliant mouse' in Device Manager

@ghost commented on GitHub (Mar 3, 2021): It occurred on my work laptop but I was using a bluetooth mouse. 'HID-compliant mouse' in Device Manager

claunia commented

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

Okay, well, that kinda ruins my theory about the trackpad. Other guesses:

Does hovering the min-max-close buttons highlight them? Do they work?
If you move the moust to like, the top-left corner of the scroll view in the settings UI, does scrolling work then?
If you open the Command Palette (Ctrl+Shift+P), does the mouse work to scroll that list?

@zadjii-msft commented on GitHub (Mar 3, 2021): Okay, well, that kinda ruins my theory about the trackpad. Other guesses: * Does hovering the min-max-close buttons highlight them? Do they work? * If you move the moust to like, the top-left corner of the scroll view in the settings UI, does scrolling work then? * If you open the Command Palette (<kbd>Ctrl+Shift+P</kbd>), does the mouse work to scroll that list?

claunia commented

@ghost commented on GitHub (Mar 7, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 7, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.

claunia commented

@ghost commented on GitHub (Mar 8, 2021):

Hovering buttons highlights them fine
Scrolling does not work anywhere in the settings UI
Scrolling does not work in the Command Palette

Issues with scrolling are with mouse only, scrolling works fine when a trackpad is used. Have tested with multiple mice.

@ghost commented on GitHub (Mar 8, 2021): - Hovering buttons highlights them fine - Scrolling does not work anywhere in the settings UI - Scrolling does not work in the Command Palette Issues with scrolling are with mouse only, scrolling works fine when a trackpad is used. Have tested with multiple mice.

claunia commented

@zadjii-msft commented on GitHub (Mar 8, 2021):

Issues with scrolling are with mouse only, scrolling works fine when a trackpad is used. Have tested with multiple mice.

what the heck? That's even weirder than I had expected. I'm gonna leave this open for now. My guess is that the hack we're doing to manually pass mouse events into the TermControl is what's making the mouse work for you in terminal tabs, but not the settings tab (or command palette). However, I'm not sure we can do that same hack for those UI elements. I don't know how to narrow the issue down more at this point, unfortunately. I'd bet that this is a Xaml Islands bug, but unsure where the root cause is exactly.

https://github.com/microsoft/PowerToys/issues/3400 also looks like another case of this, an one where they're similarly seeing this with a mouse, not a trackpad. @otaconjh Out of curiosity, which mice did you try?

@zadjii-msft commented on GitHub (Mar 8, 2021): > Issues with scrolling are with mouse only, scrolling works fine when a trackpad is used. Have tested with multiple mice. what the heck? That's even weirder than I had expected. I'm gonna leave this open for now. My guess is that the hack we're doing to manually pass mouse events into the `TermControl` is what's making the mouse work for you in terminal tabs, but not the settings tab (or command palette). However, I'm not sure we can do that same hack for those UI elements. I don't know how to narrow the issue down more at this point, unfortunately. I'd bet that this is a Xaml Islands bug, but unsure where the root cause is exactly. https://github.com/microsoft/PowerToys/issues/3400 also looks like another case of this, an one where they're similarly seeing this with a mouse, not a trackpad. @otaconjh Out of curiosity, which mice did you try?

claunia commented

@jackemerson commented on GitHub (Apr 16, 2021):

microsoft/PowerToys#3400 also looks like another case of this, an one where they're similarly seeing this with a mouse, not a trackpad. @otaconjh Out of curiosity, which mice did you try?

Just to add some additional information, this issue occurs for me across PowerToys' and Windows Terminal's settings panels. It occurs only on my desktop, and not my laptop.

Desktop

The issue occurs with any of the following mice:

Logitech MX Master 2S
Logitech G703
Steelseries RIVAL
Razer Viper Ultimate

_{...I may need to take a look at my mice hoarding habit.}

System Info

Microsoft Windows Pro 64-bit [Version 10.0.19042.928] Windows Terminal Version: 1.7.1033.0 Microsoft PowerToys Version: 0.35.0

CPU: Intel i7-7700K
GPU: NVIDIA GTX 1070

User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)

Monitor, Primary: 27", 2560 x 1440 (32 bit) (144Hz) Acer XB271HU
Monitor, Second: 34", 3440 x 1440 (32 bit) (60Hz) Dell U3419W

Laptop

For my laptop (Dell XPS 9360), there are no issues with scrolling the settings panel, with either the trackpad or with a mouse (tested with MX Master 2s & G703).

System Info

Microsoft Windows Home 64-bit [Version 10.0.19042.867] Windows Terminal Version: 1.7.1033.0 Microsoft PowerToys Version: 0.35.0

CPU: Intel i7-7500U
GPU: NVIDIA GTX 1070
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 144 DPI (150 percent)

Monitor: 13", 1920 x 1080 (32 bit) (60hz)

Changing the DPI and/or resolution for my desktop and laptop did not (respectively) allow me to, or stop me from, scrolling the settings panel.

I'll test this further with a restart following the DPI and/or resolution change, and report back.

@jackemerson commented on GitHub (Apr 16, 2021): > [microsoft/PowerToys#3400](https://github.com/microsoft/PowerToys/issues/3400) also looks like another case of this, an one where they're similarly seeing this with a mouse, not a trackpad. @otaconjh Out of curiosity, which mice did you try? Just to add some additional information, this issue occurs for me across PowerToys' and Windows Terminal's settings panels. It occurs only on my desktop, and not my laptop. ## Desktop The issue occurs with any of the following mice: - Logitech MX Master 2S - Logitech G703 - Steelseries RIVAL - Razer Viper Ultimate <sub>_...I may need to take a look at my mice hoarding habit._</sub> <details> <summary>System Info</summary> Microsoft Windows Pro 64-bit [Version 10.0.19042.928] Windows Terminal Version: 1.7.1033.0 Microsoft PowerToys Version: 0.35.0 CPU: Intel i7-7700K GPU: NVIDIA GTX 1070 User DPI Setting: 120 DPI (125 percent) System DPI Setting: 96 DPI (100 percent) Monitor, Primary: 27", 2560 x 1440 (32 bit) (144Hz) Acer XB271HU Monitor, Second: 34", 3440 x 1440 (32 bit) (60Hz) Dell U3419W </details> ## Laptop For my laptop (Dell XPS 9360), there are no issues with scrolling the settings panel, with either the trackpad or with a mouse (tested with MX Master 2s & G703). <details> <summary>System Info</summary> Microsoft Windows Home 64-bit [Version 10.0.19042.867] Windows Terminal Version: 1.7.1033.0 Microsoft PowerToys Version: 0.35.0 CPU: Intel i7-7500U GPU: NVIDIA GTX 1070 User DPI Setting: 144 DPI (150 percent) System DPI Setting: 144 DPI (150 percent) Monitor: 13", 1920 x 1080 (32 bit) (60hz) </details> Changing the DPI and/or resolution for my desktop and laptop did not (respectively) allow me to, or stop me from, scrolling the settings panel. I'll test this further with a restart following the DPI and/or resolution change, and report back.

claunia commented

@loopervfx commented on GitHub (Jun 1, 2021):

I am also unable to scroll in Terminal v1.8.1444.0 Settings, I'm using a Kensington Expert Mouse Wired Trackball (USB) on Windows 10 ver 1909 build 18363.1379

@loopervfx commented on GitHub (Jun 1, 2021): I am also unable to scroll in Terminal v1.8.1444.0 Settings, I'm using a Kensington Expert Mouse Wired Trackball (USB) on Windows 10 ver 1909 build 18363.1379

claunia commented

@jaortizco commented on GitHub (Jun 9, 2021):

I have the same problem, I can scroll everywhere with my touchpad (Synaptics) except in the settings tab. It works fine when I use my Bluetooth mouse.

Windows Terminal
Version: 1.8.1521.0

@jaortizco commented on GitHub (Jun 9, 2021): I have the same problem, I can scroll everywhere with my touchpad (Synaptics) except in the settings tab. It works fine when I use my Bluetooth mouse. Windows Terminal Version: 1.8.1521.0

claunia commented

@timadye commented on GitHub (Jul 23, 2021):

I had this same issue, but only in a specific set of circumstances, and now have a work-around. Here's what I observed:

Scroll doesn't work in Settings tab only (works in Terminal tabs)
Only with an external mouse (Evoluent VerticalMouse2; not tested with other external mice). Trackpad scrolling works on two different laptops.
Only when I have X-Mouse Button Control enabled and have the (default) option to "scroll window under cursor". Note that the behaviour is the same whether or not Windows Terminal is the active window.

That last point indicates that it's something going on with XMBC. If it were a problem, I could take it up with them. But actually it's easier just to "Disable Scroll Window Under Cursor".

That option doesn't seem to do anything - I guess Windows now has this behaviour built-in, so there's no need to have XMBC do it. I didn't see a problem like this before I saw it in Windows Terminal Settings, so there is some funny interaction between the two programs.

I hope that gives a clue as to what's going on for other people who aren't so lucky to have an easy fix as (it looks like) I have. It might be possible for a developer to reproduce the issue by installing XMBC (making sure that option is not selected) and using an external mouse.

So this isn't a problem for me, but I hope my observation helps.
Tim.

Windows Terminal v1.9.1942.0.
X-Mouse Button Control v2.19.2.
Windows 10 20H2.

@timadye commented on GitHub (Jul 23, 2021): I had this same issue, but only in a specific set of circumstances, and now have a work-around. Here's what I observed: * Scroll doesn't work in Settings tab only (works in Terminal tabs) * Only with an external mouse (Evoluent VerticalMouse2; not tested with other external mice). Trackpad scrolling works on two different laptops. * Only when I have [X-Mouse Button Control](https://www.highrez.co.uk/downloads/XMouseButtonControl.htm) enabled and have the (default) option to "scroll window under cursor". Note that the behaviour is the same whether or not Windows Terminal is the active window. That last point indicates that it's something going on with XMBC. If it were a problem, I could take it up with them. But actually it's easier just to "Disable Scroll Window Under Cursor". ![XMBC](https://user-images.githubusercontent.com/115933/126824449-3111d4c2-31ee-438f-92ae-0eae75fffe4d.PNG) That option doesn't seem to do anything - I guess Windows now has this behaviour built-in, so there's no need to have XMBC do it. I didn't see a problem like this before I saw it in Windows Terminal Settings, so there is some funny interaction between the two programs. I hope that gives a clue as to what's going on for other people who aren't so lucky to have an easy fix as (it looks like) I have. It might be possible for a developer to reproduce the issue by installing XMBC (making sure that option is not selected) and using an external mouse. So this isn't a problem for me, but I hope my observation helps. Tim. Windows Terminal v1.9.1942.0. X-Mouse Button Control v2.19.2. Windows 10 20H2.

claunia commented

@jackemerson commented on GitHub (Jul 25, 2021):

Well, you're absolutely right. I've run XMBC for so long, I didn't even consider it. 😑

So disabling the relevant Global Setting:

or (as you mentioned, also) disabling it on a matched profile sorts this issue out.

Cheers, Tim!

@jackemerson commented on GitHub (Jul 25, 2021): Well, you're absolutely right. I've run XMBC for so long, I didn't even consider it. 😑 So disabling the relevant Global Setting: ![image](https://user-images.githubusercontent.com/12045357/126883342-30e0ca8b-78a2-4d9e-9cd0-95d946a2ff2d.png) or (as you mentioned, also) disabling it on a matched profile sorts this issue out. Cheers, Tim!

claunia commented

@loopervfx commented on GitHub (Jul 25, 2021):

I also use X-Mouse Button Control and @timadye's workaround resolved the issue for me. @jackemerson's option also worked and is a less error prone solution in the long run. Same results for PowerToys settings scroll issue https://github.com/microsoft/PowerToys/issues/3400

@loopervfx commented on GitHub (Jul 25, 2021): I also use X-Mouse Button Control and @timadye's workaround resolved the issue for me. @jackemerson's option also worked and is a less error prone solution in the long run. Same results for PowerToys settings scroll issue https://github.com/microsoft/PowerToys/issues/3400

claunia commented

@zadjii-msft commented on GitHub (Jul 26, 2021):

Wow that's crazy. Glad someone was able to get to the bottom of this!

@zadjii-msft commented on GitHub (Jul 26, 2021): Wow that's crazy. Glad someone was able to get to the bottom of this!

claunia commented

@loopervfx commented on GitHub (Jul 26, 2021):

Wow that's crazy. Glad someone was able to get to the bottom of this!

for posterity sake, this issue hasn't been isolated / confirmed to be caused by X-Mouse Button Control or due to a conflict with this software exclusively. Only that a workaround has been found in this case. According to reports here and in the still open Power toys sister issue, This maybe also be happening with Synaptics and/or Logitech input devices, due to a conflict or flaw with their configuration software, drivers, and/or Windows.

@loopervfx commented on GitHub (Jul 26, 2021): > Wow that's crazy. Glad someone was able to get to the bottom of this! for posterity sake, this issue hasn't been isolated / confirmed to be caused by X-Mouse Button Control or due to a conflict with this software exclusively. Only that a workaround has been found in this case. According to reports here and in the still open Power toys sister issue, This maybe also be happening with Synaptics and/or Logitech input devices, due to a conflict or flaw with their configuration software, drivers, and/or Windows.

claunia commented

@rozele commented on GitHub (Sep 14, 2021):

This issue also repro's when using WizMouse.

@rozele commented on GitHub (Sep 14, 2021): This issue also repro's when using WizMouse.

claunia commented

@rozele commented on GitHub (Sep 29, 2021):

In case anyone is interested, I implemented a workaround for this for a react-native-windows app built on XAML Islands:
https://gist.github.com/rozele/a4b26810b9a4f68373e421a49d06a5ab

@rozele commented on GitHub (Sep 29, 2021): In case anyone is interested, I implemented a workaround for this for a react-native-windows app built on XAML Islands: https://gist.github.com/rozele/a4b26810b9a4f68373e421a49d06a5ab

claunia commented