Touchpad scrolling not possible #1311

@zadjii-msft commented on GitHub (May 24, 2019):

Can you try setting a breakpoint in TermControl::_MouseScrollHandler to see if that's getting hit?

Two-finger scrolling works just fine with my surfacebook, so I'm thinking that it's something specific to your device.

@zadjii-msft commented on GitHub (May 24, 2019): Can you try setting a breakpoint in `TermControl::_MouseScrollHandler` to see if that's getting hit? Two-finger scrolling works just fine with my surfacebook, so I'm thinking that it's something specific to your device.

claunia commented

@Paul-Weisser commented on GitHub (May 24, 2019):

Okay I'm starting to feel a little stupid. I cleaned the solution and build CascadiaPackage on Debug x64 with the breakpoints in TermControl::_MouseScrollHandler but it wont stop there.

I need a little help how to get VS (2019) stopping at this class...

@Paul-Weisser commented on GitHub (May 24, 2019): Okay I'm starting to feel a little stupid. I cleaned the solution and build CascadiaPackage on Debug x64 with the breakpoints in `TermControl::_MouseScrollHandler` but it wont stop there. I need a little help how to get VS (2019) stopping at this class...

claunia commented

@DHowett-MSFT commented on GitHub (May 24, 2019):

You might be in need of this debugging doc.

@DHowett-MSFT commented on GitHub (May 24, 2019): You might be in need of [this debugging doc](https://github.com/microsoft/terminal/blob/master/doc/Debugging.md).

claunia commented

@zadjii-msft commented on GitHub (May 24, 2019):

Maybe try something that you can be sure is hitting, like TermControl::_KeyDownHandler

@zadjii-msft commented on GitHub (May 24, 2019): Maybe try something that you can be sure is hitting, like `TermControl::_KeyDownHandler`

claunia commented

@Paul-Weisser commented on GitHub (May 25, 2019):

Thanks @DHowett-MSFT, missed that one!

But now with a working debug-mode there are several memory-violation-exceptions popping by twinapi.appcore.dll which my VS for some reason cannot ignore... (The terminal does not crash though)
So I am not able to reach the breakpoints...

Since it seems like nobody else is having these issues I will let it be and accept the fact, that something is wrong with my maschine. But I think its still interesting, that the new terminal is the only app where I am unable to scroll with two fingers.

@Paul-Weisser commented on GitHub (May 25, 2019): Thanks @DHowett-MSFT, missed that one! But now with a working debug-mode there are several memory-violation-exceptions popping by twinapi.appcore.dll which my VS for some reason cannot ignore... (The terminal does not crash though) So I am not able to reach the breakpoints... ![grafik](https://user-images.githubusercontent.com/34196171/58360801-f3a87180-7e8a-11e9-8452-9c6c4a6655ea.png) Since it seems like nobody else is having these issues I will let it be and accept the fact, that something is wrong with my maschine. But I think its still interesting, that the new terminal is the only app where I am unable to scroll with two fingers.

claunia commented

@rehnarama commented on GitHub (May 26, 2019):

I have this issue as well though!

My touchpad uses the Synaptics ClickPad drivers, not microsoft precision drivers, perhaps there is an issue there?

@rehnarama commented on GitHub (May 26, 2019): I have this issue as well though! My touchpad uses the Synaptics ClickPad drivers, not microsoft precision drivers, perhaps there is an issue there?

claunia commented

@rehnarama commented on GitHub (May 26, 2019):

@zadjii-msft , After some debugging:

Can you try setting a breakpoint in TermControl::_MouseScrollHandler to see if that's getting hit?

Two-finger scrolling works just fine with my surfacebook, so I'm thinking that it's something specific to your device.

The PointerWheelChanged handler bound to TermControl::_MouseScrollHandler is never called.

Maybe try something that you can be sure is hitting, like TermControl::_KeyDownHandler

All other pointer handlers (and key handlers) work as expected.

@rehnarama commented on GitHub (May 26, 2019): @zadjii-msft , After some debugging: > Can you try setting a breakpoint in `TermControl::_MouseScrollHandler` to see if that's getting hit? > > Two-finger scrolling works just fine with my surfacebook, so I'm thinking that it's something specific to your device. The PointerWheelChanged handler bound to TermControl::_MouseScrollHandler is never called. > Maybe try something that you can be sure is hitting, like `TermControl::_KeyDownHandler` All other pointer handlers (and key handlers) work as expected.

claunia commented

@Paul-Weisser commented on GitHub (May 26, 2019):

@rehnarama
I tried both, Microsoft and synaptics drivers
Maybe it's an locale issue (I'm on a German locale)
Since there have been other issues regarding locale and getting user-input right?

@Paul-Weisser commented on GitHub (May 26, 2019): @rehnarama I tried both, Microsoft and synaptics drivers Maybe it's an locale issue (I'm on a German locale) Since there have been other issues regarding locale and getting user-input right?

claunia commented

@rehnarama commented on GitHub (May 27, 2019):

@rehnarama
I tried both, Microsoft and synaptics drivers
Maybe it's an locale issue (I'm on a German locale)
Since there have been other issues regarding locale and getting user-input right?

Could be, (Swedish locale here at least). I've also tried a minimal UWP app, and there were no problem with firing the PointerWheelChanged event there.

I've just now noticed that, when disabling "Scroll Inactive Windows" in settings, the scrolling with an external mouse becomes unreliable as well! With unreliable I mean it works sometimes (when hovering over rendered text?), and then suddenly stops working (usually when trying to scroll empty area, but not always).

Since scrolling inactive windows doesn't work with synaptics drivers, it might be a focusing issue of some sorts? Or perhaps turning off "Scroll Inactive Windows" setting would be a seperate issue?

@rehnarama commented on GitHub (May 27, 2019): > @rehnarama > I tried both, Microsoft and synaptics drivers > Maybe it's an locale issue (I'm on a German locale) > Since there have been other issues regarding locale and getting user-input right? Could be, (Swedish locale here at least). I've also tried a minimal UWP app, and there were no problem with firing the PointerWheelChanged event there. --- I've just now noticed that, when disabling "Scroll Inactive Windows" in settings, the scrolling with an external mouse becomes unreliable as well! With unreliable I mean it works sometimes (when hovering over rendered text?), and then suddenly stops working (usually when trying to scroll empty area, but not always). Since scrolling inactive windows doesn't work with synaptics drivers, it might be a focusing issue of some sorts? Or perhaps turning off "Scroll Inactive Windows" setting would be a seperate issue?

claunia commented

@zadjii-msft commented on GitHub (May 28, 2019):

I really doubt that locale would affect mouse input, but I guess I'm not an expert in the input stack.

The "scroll inactive windows think" might be a good lead on tracking this bug down though. Considering I don't believe anyone on the dev team has a device this is reproing on, the more help we can get the better :)

@zadjii-msft commented on GitHub (May 28, 2019): I _really_ doubt that locale would affect mouse input, but I guess I'm not an expert in the input stack. The "scroll inactive windows think" might be a good lead on tracking this bug down though. Considering I don't believe anyone on the dev team has a device this is reproing on, the more help we can get the better :)

claunia commented

@Paul-Weisser commented on GitHub (May 28, 2019):

I can't dig into this for the next four weeks...
If nobody else fixes this until then I will have a closer look (after I fixed the weird memory access violation...)

@Paul-Weisser commented on GitHub (May 28, 2019): I can't dig into this for the next four weeks... If nobody else fixes this until then I will have a closer look (after I fixed the weird memory access violation...)

claunia commented

@DHowett-MSFT commented on GitHub (Jun 1, 2019):

Hey, I think the memory access violation is a bad interaction with Visual Studio.

Can you go into Options, search for xaml, and turn off live Xaml UI/visual tree debugging? It'll unload the "UWP Tap," which seems to cause an access violation for some people during startup.

@DHowett-MSFT commented on GitHub (Jun 1, 2019): Hey, I think the memory access violation is a bad interaction with Visual Studio. Can you go into Options, search for `xaml`, and turn off live Xaml UI/visual tree debugging? It'll unload the "UWP Tap," which seems to cause an access violation for _some people_ during startup.

claunia commented

@Paul-Weisser commented on GitHub (Jun 1, 2019):

@DHowett-MSFT Thanks! That totally worked!👍

Now I was able to reproduce the behaviour @rehnarama was experiencing.

@Paul-Weisser commented on GitHub (Jun 1, 2019): @DHowett-MSFT Thanks! That totally worked!👍 Now I was able to reproduce the behaviour @rehnarama was experiencing.

claunia commented

@dkter commented on GitHub (Jun 6, 2019):

My touchpad (Alps drivers) doesn't work either.

Then again, neither does my mouse scroll wheel. Maybe something's wrong with my build.

@dkter commented on GitHub (Jun 6, 2019): My touchpad (Alps drivers) doesn't work either. Then again, neither does my mouse scroll wheel. Maybe something's wrong with my build.

claunia commented

@Navino16 commented on GitHub (Jun 26, 2019):

Hello,

I can't scroll with my touchpad (Synaptics) also but I can scroll with other mouse.
If you need more info, let me know

@Navino16 commented on GitHub (Jun 26, 2019): Hello, I can't scroll with my touchpad (Synaptics) also but I can scroll with other mouse. If you need more info, let me know

claunia commented

@Paul-Weisser commented on GitHub (Jun 28, 2019):

Tracking this issue down I found this issue in the microsoft/microsoft-ui-xaml repo.
It seems like we got a similar problem here, but I can't say for sure since I don't know enough about our architecture. @zadjii-msft could you please confirm that the structure of the new terminal would apply to this? Thanks!

@Paul-Weisser commented on GitHub (Jun 28, 2019): Tracking this issue down I found [this issue](https://github.com/microsoft/microsoft-ui-xaml/issues/760) in the microsoft/microsoft-ui-xaml repo. It seems like we got a similar problem here, but I can't say for sure since I don't know enough about our architecture. @zadjii-msft could you please confirm that the structure of the new terminal would apply to this? Thanks!

claunia commented

@zadjii-msft commented on GitHub (Jul 1, 2019):

That looks like it's the root cause of the issue at hand here. I'm going to close this issue as a dupe of that XAML issue.

When microsoft/microsoft-ui-xaml#760 is fixed, this should be fixed for us.

@zadjii-msft commented on GitHub (Jul 1, 2019): That looks like it's the root cause of the issue at hand here. I'm going to close this issue as a dupe of that XAML issue. When microsoft/microsoft-ui-xaml#760 is fixed, this should be fixed for us.

claunia commented

@Austin-Lamb commented on GitHub (Jul 2, 2019):

@zadjii-msft - unfortunately the fix for Microsoft-ui-xaml#760 won't fix this for Terminal. That fix will only help ScrollViewer controls, but Terminal will need to implement its own scrolling as you're drawing your own stuff and doing your own scrolling in the Terminal app code. I recommend reactivating this issue.

@Austin-Lamb commented on GitHub (Jul 2, 2019): @zadjii-msft - unfortunately the fix for Microsoft-ui-xaml#760 won't fix this for Terminal. That fix will only help ScrollViewer controls, but Terminal will need to implement its own scrolling as you're drawing your own stuff and doing your own scrolling in the Terminal app code. I recommend reactivating this issue.

claunia commented

@DHowett-MSFT commented on GitHub (Jul 2, 2019):

I thought we might actually be using ScrollViewer, but it turns out we aren't.

@DHowett-MSFT commented on GitHub (Jul 2, 2019): I thought we might actually be using ScrollViewer, but it turns out we aren't.

claunia commented

@Paul-Weisser commented on GitHub (Jul 4, 2019):

So, I'm not sure how to fix this.

If I decrypted this right we are just listening for the PointerWheelChanged-event in the _root Controls::Grid, which is an implementation of Windows::UI::Xaml::Controls::IGrid, but this never gets called from my touchpad.

So if the Microsoft-ui-xaml#760-fix really isn't fixing this we would need to write a new mousewheel-input-handler...

@Paul-Weisser commented on GitHub (Jul 4, 2019): So, I'm not sure how to fix this. If I decrypted this right we are just listening for the `PointerWheelChanged`-event in the `_root` `Controls::Grid`, which is an implementation of `Windows::UI::Xaml::Controls::IGrid`, but this never gets called from my touchpad. So if the Microsoft-ui-xaml#760-fix really isn't fixing this we would need to write a new mousewheel-input-handler...

claunia commented

@Escapingbug commented on GitHub (Jul 30, 2019):

Same issue here. And my mouse wheel not working as well as I tested (develop build on master branch, not sure if other branches have fixed this).
I did set up a breakpoint at _MouseWheelHandler and found out when ctrl is hold, it is actually called. But without ctrl holding, it is not even called.

It really seems to be an ui or xaml related issue..

What annoys me is that currently tab cannot show all the tabs we have even as I have no scrolling support.

@Escapingbug commented on GitHub (Jul 30, 2019): Same issue here. And my mouse wheel not working as well as I tested (develop build on master branch, not sure if other branches have fixed this). I did set up a breakpoint at `_MouseWheelHandler` and found out when `ctrl` is hold, it is actually called. But without `ctrl` holding, it is not even called. It really seems to be an ui or xaml related issue.. What annoys me is that currently tab cannot show all the tabs we have even as I have no scrolling support.

claunia commented

2026-01-30 22:22:07 +00:00

@waelkdouh commented on GitHub (Aug 28, 2019):

I have a surfacebook and scrolling is not working using external surface mouse or the trackpad.

@waelkdouh commented on GitHub (Aug 28, 2019): I have a surfacebook and scrolling is not working using external surface mouse or the trackpad.

claunia commented

@Uxorious commented on GitHub (Aug 31, 2019):

Also not working on HP Spectre x360.

@Uxorious commented on GitHub (Aug 31, 2019): Also not working on HP Spectre x360.

claunia commented

2026-01-30 22:22:07 +00:00

@jj10133 commented on GitHub (Sep 19, 2019):

I'm sure the scrolling either on the touchpad or using a mouse doesn't get detected in most of the laptops and computers

@jj10133 commented on GitHub (Sep 19, 2019): I'm sure the scrolling either on the touchpad or using a mouse doesn't get detected in most of the laptops and computers

claunia commented

2026-01-30 22:22:07 +00:00

@joshschmelzle commented on GitHub (Sep 21, 2019):

I also have this issue with both the TrackPad and TrackPoint on a Lenovo T450 touchpad (Synaptics drivers).

@joshschmelzle commented on GitHub (Sep 21, 2019): I also have this issue with both the TrackPad and TrackPoint on a Lenovo T450 touchpad (Synaptics drivers).

claunia commented

2026-01-30 22:22:08 +00:00

@pamtbaau commented on GitHub (Sep 21, 2019):

Scrolling with touchpad does work (for me) when in selection mode (left touchpad button pressed). Haven't tried an external mouse.

@pamtbaau commented on GitHub (Sep 21, 2019): Scrolling with touchpad **does** work (for me) when in selection mode (left touchpad button pressed). Haven't tried an external mouse.

claunia commented

2026-01-30 22:22:08 +00:00

@dkter commented on GitHub (Sep 22, 2019):

Scrolling with touchpad does work when in selection mode (left touchpad button pressed).

It doesn't for me.

@dkter commented on GitHub (Sep 22, 2019): > > > Scrolling with touchpad **does** work when in selection mode (left touchpad button pressed). It doesn't for me.

claunia commented

2026-01-30 22:22:09 +00:00

@tu-naive commented on GitHub (Sep 25, 2019):

Synaptics trackpad scrolling does not work. Mouse middle-button scrolling works.

@tu-naive commented on GitHub (Sep 25, 2019): Synaptics trackpad scrolling does not work. Mouse middle-button scrolling works.

claunia commented

2026-01-30 22:22:09 +00:00

@DerAlbertCom commented on GitHub (Oct 9, 2019):

Just for Information, I have a Precision Touch Pad (Dell XPS 15, 9560), I think with Microsoft Precision Driver. Two finger Scrolling works fine. Also scrolling with a Surface Sculpt Mouse works fine (no Driver o additional Software installed). I don't press additional Keys. Termina: V0.5.2762.0 Windows: v10.0.18362.418

@DerAlbertCom commented on GitHub (Oct 9, 2019): Just for Information, I have a Precision Touch Pad (Dell XPS 15, 9560), I think with Microsoft Precision Driver. Two finger Scrolling works fine. Also scrolling with a Surface Sculpt Mouse works fine (no Driver o additional Software installed). I don't press additional Keys. Termina: V0.5.2762.0 Windows: v10.0.18362.418

claunia commented

2026-01-30 22:22:10 +00:00

@sonnypate commented on GitHub (Oct 17, 2019):

I'm also having this issue where my touchpad or external mouse will not scroll up. It works for a while if I restart my computer, but then suddenly it stops working. I noticed that all UWP apps have the same problem (my Start Menu, Weather app etc). Once scrolling stops working on one of them, it stops on all UWP-based applications. This has been an issue on every computer I've used, so it doesn't seem to be based on specific hardware. My current set up is a Dell XPS 17 and a Logitech MX Master 2s, scrolling stops working on both the touchpad and mouse at the same time when it happens. I haven't been able to figure out what triggers it, because some days i'll make it half way through the day before it stops working and the only fix is to reboot.

@sonnypate commented on GitHub (Oct 17, 2019): I'm also having this issue where my touchpad or external mouse will not scroll up. It works for a while if I restart my computer, but then suddenly it stops working. I noticed that all UWP apps have the same problem (my Start Menu, Weather app etc). Once scrolling stops working on one of them, it stops on all UWP-based applications. This has been an issue on every computer I've used, so it doesn't seem to be based on specific hardware. My current set up is a Dell XPS 17 and a Logitech MX Master 2s, scrolling stops working on both the touchpad and mouse at the same time when it happens. I haven't been able to figure out what triggers it, because some days i'll make it half way through the day before it stops working and the only fix is to reboot.

claunia commented

2026-01-30 22:22:10 +00:00

@mysticatea commented on GitHub (Oct 29, 2019):

I have encountered likely this problem. I'm using ThinkPad Compact USB Keyboard with TrackPoint and the TrackPoint doesn't scroll Windows Terminal (Preview). For a reference, TrackPoint works fine on cmd.exe, Windows PowerShell, and Visual Studio Code's integrated terminal.

Windows 10 1903 (18362.418)
Windows Terminal (Preview) 0.6.2951.0

@mysticatea commented on GitHub (Oct 29, 2019): I have encountered likely this problem. I'm using [ThinkPad Compact USB Keyboard with TrackPoint](https://support.lenovo.com/ro/ro/solutions/pd026745) and the TrackPoint doesn't scroll Windows Terminal (Preview). For a reference, TrackPoint works fine on cmd.exe, Windows PowerShell, and Visual Studio Code's integrated terminal. - Windows 10 1903 (18362.418) - Windows Terminal (Preview) 0.6.2951.0

claunia commented

2026-01-30 22:22:11 +00:00

@fourpastmidnight commented on GitHub (Nov 8, 2019):

I'm using a Clevo P370EM with a Synaptics touchpad. I also cannot scroll using two-finger scrolling or edge scrolling.

@fourpastmidnight commented on GitHub (Nov 8, 2019): I'm using a Clevo P370EM with a Synaptics touchpad. I also cannot scroll using two-finger scrolling or edge scrolling.

claunia commented

2026-01-30 22:22:11 +00:00

@humble-b commented on GitHub (Nov 14, 2019):

When holding left shift key, scrolling works with external mouse. CTRL key zooms in or out with external mouse wheel.
I work from a desktop computer and not laptop with english-us locale

@humble-b commented on GitHub (Nov 14, 2019): When holding left shift key, scrolling works with external mouse. CTRL key zooms in or out with external mouse wheel. I work from a desktop computer and not laptop with english-us locale

claunia commented

2026-01-30 22:22:11 +00:00

@dkter commented on GitHub (Nov 17, 2019):

When holding left shift key, scrolling works with external mouse.

I can confirm this. TermControl::_MouseWheelHandler is only called if Ctrl or Shift (or both) are pressed (other modifiers don't affect it). This is the case for both my touchpad and my USB mouse scroll wheel.

@dkter commented on GitHub (Nov 17, 2019): >When holding left shift key, scrolling works with external mouse. I can confirm this. `TermControl::_MouseWheelHandler` is only called if Ctrl or Shift (or both) are pressed (other modifiers don't affect it). This is the case for both my touchpad and my USB mouse scroll wheel.

claunia commented

2026-01-30 22:22:12 +00:00

@dkter commented on GitHub (Nov 17, 2019):

Same behaviour on the new TabView. Scrolling normally doesn't do anything, while Shift-scrolling works (Ctrl-scrolling also doesn't work, but I haven't tested if the handler is being called yet). This leads me to believe it could be a WinUI bug...

edit: the TabView in the XAML Controls Gallery app behaves normally.

@dkter commented on GitHub (Nov 17, 2019): Same behaviour on the new TabView. Scrolling normally doesn't do anything, while Shift-scrolling works (Ctrl-scrolling also doesn't work, but I haven't tested if the handler is being called yet). This leads me to believe it could be a WinUI bug... edit: the TabView in the XAML Controls Gallery app behaves normally.

claunia commented

2026-01-30 22:22:12 +00:00

@Uxorious commented on GitHub (Nov 28, 2019):

No touchpad scrolling is working for me.
And on the latest version, the scrollbar on the right doesn't work either :-(

@Uxorious commented on GitHub (Nov 28, 2019): No touchpad scrolling is working for me. And on the latest version, the scrollbar on the right doesn't work either :-(

claunia commented

2026-01-30 22:22:12 +00:00

@fourpastmidnight commented on GitHub (Nov 28, 2019):

I’ve had instances where the scroll bar stopped working, too, though the scroll arrows still worked. I believe it you change tabs or open a new console tab, the scroll bar starts working again.

Sent from my Windows 10 phone

From: Uxorious
Sent: Thursday, November 28, 2019 11:21
To: microsoft/terminal
Cc: Craig E. Shea; Comment
Subject: Re: [microsoft/terminal] Touchpad scrolling not possible (#979)

No touchpad scrolling is working for me.
And on the latest version, the scrollbar on the right doesn't work either :-(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@fourpastmidnight commented on GitHub (Nov 28, 2019): I’ve had instances where the scroll bar stopped working, too, though the scroll arrows still worked. I believe it you change tabs or open a new console tab, the scroll bar starts working again. Sent from my Windows 10 phone From: Uxorious Sent: Thursday, November 28, 2019 11:21 To: microsoft/terminal Cc: Craig E. Shea; Comment Subject: Re: [microsoft/terminal] Touchpad scrolling not possible (#979) No touchpad scrolling is working for me. And on the latest version, the scrollbar on the right doesn't work either :-( — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

claunia commented

@dkter commented on GitHub (Nov 28, 2019):

@fourpastmidnight I've had this issue as well, but I can't tell if it's related.

@dkter commented on GitHub (Nov 28, 2019): @fourpastmidnight I've had this issue as well, but I can't tell if it's related.

claunia commented

@waelkdouh commented on GitHub (Dec 12, 2019):

I have a surfacebook and scrolling is not working using external surface mouse or the trackpad.

Turns out the culprit was an app I had installed on my machine called x-mouse

@waelkdouh commented on GitHub (Dec 12, 2019): > I have a surfacebook and scrolling is not working using external surface mouse or the trackpad. Turns out the culprit was an app I had installed on my machine called x-mouse

claunia commented

@dkter commented on GitHub (Dec 12, 2019):

Turns out the culprit was an app I had installed on my machine called x-mouse

This was my issue as well

@dkter commented on GitHub (Dec 12, 2019): > Turns out the culprit was an app I had installed on my machine called x-mouse This was my issue as well

claunia commented

2026-01-30 22:22:14 +00:00

@shivasurya commented on GitHub (Dec 13, 2019):

any updates please

@shivasurya commented on GitHub (Dec 13, 2019): any updates please

claunia commented

@zadjii-msft commented on GitHub (Dec 13, 2019):

@shivasurya When we have updates to share, we'll make sure to post in the thread. I don't believe there's anyone on the team with hardware that repros this currently, so if someone in the community could help contribute a fix for this, we'd certainly appreciate it. As it currently stands, we'll make sure to get this fixed before the 1.0 release of the terminal, but we don't have a more specific timeframe set.

@zadjii-msft commented on GitHub (Dec 13, 2019): @shivasurya When we have updates to share, we'll make sure to post in the thread. I don't believe there's anyone on the team with hardware that repros this currently, so if someone in the community could help contribute a fix for this, we'd certainly appreciate it. As it currently stands, we'll make sure to get this fixed before the 1.0 release of the terminal, but we don't have a more specific timeframe set.

claunia commented

2026-01-30 22:22:14 +00:00

@jsnfwlr commented on GitHub (Dec 16, 2019):

Turns out the culprit was an app I had installed on my machine called x-mouse

To keep X-Mouse and still allow scroll in Microsoft Terminal, just disable "Make scroll wheel scroll window under cursor" in the X-Mouse settings.

@jsnfwlr commented on GitHub (Dec 16, 2019): > Turns out the culprit was an app I had installed on my machine called x-mouse To keep X-Mouse and still allow scroll in Microsoft Terminal, just disable "Make scroll wheel scroll window under cursor" in the X-Mouse settings.

claunia commented

@wisammechano commented on GitHub (Dec 28, 2019):

I am also having this issue my laptop is HP Omen with windows 10 pro. The touchpad 2-finger scrolling is not working. Synaptics touchpad.

The only way to scroll is using ctrl+up,down

@wisammechano commented on GitHub (Dec 28, 2019): I am also having this issue my laptop is HP Omen with windows 10 pro. The touchpad 2-finger scrolling is not working. Synaptics touchpad. The only way to scroll is using ctrl+up,down

claunia commented

@Ade-Joshe commented on GitHub (Feb 19, 2020):

this issue has been pending for quite some time now, I would really appreciate a fix.
In the main time, I just go with ctrl + shift + up/down key.

Better than nothing

@Ade-Joshe commented on GitHub (Feb 19, 2020): this issue has been pending for quite some time now, I would really appreciate a fix. In the main time, I just go with ctrl + shift + up/down key. Better than nothing

claunia commented

@DHowett-MSFT commented on GitHub (Feb 24, 2020):

#4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

@DHowett-MSFT commented on GitHub (Feb 24, 2020): #4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

claunia commented

@rehnarama commented on GitHub (Feb 24, 2020):

#4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

Nope, not here at least. Scrolling works fine in Store with my touchpad, but does not work in Terminal.

@rehnarama commented on GitHub (Feb 24, 2020): > > > #4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior? Nope, not here at least. Scrolling works fine in Store with my touchpad, but does not work in Terminal.

claunia commented

@jj10133 commented on GitHub (Feb 25, 2020):

everyone who has issues on trying to scroll i would say check out again. My problem is fixed

@jj10133 commented on GitHub (Feb 25, 2020): everyone who has issues on trying to scroll i would say check out again. My problem is fixed

claunia commented

@sonnypate commented on GitHub (Feb 26, 2020):

#4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it.

@sonnypate commented on GitHub (Feb 26, 2020): > > > #4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior? Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it.

claunia commented

@vangorden commented on GitHub (Feb 26, 2020):

#4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it.

My issue sounds very different from yours. Scrolling works perfectly everywhere except in Windows Terminal where two finger scrolling has never worked (mouse wheel works fine). I suspect it is related to the way the Synaptic touchpad reports scroll events. I'm using an HP Spectre x360.

@vangorden commented on GitHub (Feb 26, 2020): > > > > #4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior? > > Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it. My issue sounds very different from yours. Scrolling works perfectly everywhere except in Windows Terminal where two finger scrolling has never worked (mouse wheel works fine). I suspect it is related to the way the Synaptic touchpad reports scroll events. I'm using an HP Spectre x360.

claunia commented

@sonnypate commented on GitHub (Mar 2, 2020):

#4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior?

Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it.

My issue sounds very different from yours. Scrolling works perfectly everywhere except in Windows Terminal where two finger scrolling has never worked (mouse wheel works fine). I suspect it is related to the way the Synaptic touchpad reports scroll events. I'm using an HP Spectre x360.

So I found the issue with my scrolling. We use a Java based application that's causing the issue. If I close that application I can scroll in the terminal, store, and Start Menu, but it happens to be an application that I use for most of the day, so I never closed it before to test.

@sonnypate commented on GitHub (Mar 2, 2020): > > > > > #4700 came with a report that scrolling doesn't work in Store, either. Is anyone else here seeing the same behavior? > > > > > > Scrolling works for me in both the store and the terminal when I reboot, but after a random amount of time, they both stop working (including the Start menu, and any other application built off the same platform). I'm starting to think it might be my antivirus because it will affect all computers where I work, and the only thing in common is the antivirus between them. We don't use anything like x-mouse, and all computers have the "Scroll inactive windows when I hover over them" setting enabled. Once it stops working, nothing seems to fix it other than a reboot. I've tried removing the mouse, adding it back, changing the mouse, closing and reopening the terminal, killing and relaunching explorer.exe, disabling the scroll inactive windows setting then reenabling it. Nothing other than a reboot seems to fix it. > > My issue sounds very different from yours. Scrolling works perfectly everywhere except in Windows Terminal where two finger scrolling has never worked (mouse wheel works fine). I suspect it is related to the way the Synaptic touchpad reports scroll events. I'm using an HP Spectre x360. So I found the issue with my scrolling. We use a Java based application that's causing the issue. If I close that application I can scroll in the terminal, store, and Start Menu, but it happens to be an application that I use for most of the day, so I never closed it before to test.

claunia commented

@msbrunoalves commented on GitHub (Mar 11, 2020):

I think this is the same issue I've had with different programs over the years. Synaptics drivers implement scrolling in a different way than they should, I've had issues with VM's and some random specific apps that wouldn't scroll with the touchpad.
It really shouldn't be an issue for the terminal though, Powershell and CMD standalone scroll with no issues, so I'm guessing the Terminal app handles scrolling in a different way.

@msbrunoalves commented on GitHub (Mar 11, 2020): I think this is the same issue I've had with different programs over the years. Synaptics drivers implement scrolling in a different way than they should, I've had issues with VM's and some random specific apps that wouldn't scroll with the touchpad. It really shouldn't be an issue for the terminal though, Powershell and CMD standalone scroll with no issues, so I'm guessing the Terminal app handles scrolling in a different way.

claunia commented

@tukusejssirs commented on GitHub (Mar 17, 2020):

This affects me on Win10 Build 18363.720 and Windows Terminal v0.9.433.0.

I cannot scroll using mouse (but I can scroll other windows), I wish I could scroll at least with Shift+PgUp and Shift+PgDn (I still need to check if there is a keybinding command to set the shortcuts for it).

Currently, the only way to scroll the output is using the the mouse clicking of the scrollbar.

Update: Just an OT update that with command list from the Settings Schema, I was able to add the keybindings from scrolling (note that scrollUp scrolls a line up and scrollUpPage scrolls a page up; same from scrolling down):

{
	"command": "scrollDownPage",
	"keys": [
		"shift+pgdn"
	]
},
{
	"command": "scrollUpPage",
	"keys": [
		"shift+pgup"
	]
}

@tukusejssirs commented on GitHub (Mar 17, 2020): This affects me on Win10 Build 18363.720 and Windows Terminal v0.9.433.0. I cannot scroll using mouse (but I can scroll other windows), I wish I could scroll at least with <kbd>Shift</kbd>+<kbd>PgUp</kbd> and <kbd>Shift</kbd>+<kbd>PgDn</kbd> (I still need to check if there is a keybinding `command` to set the shortcuts for it). Currently, the only way to scroll the output is using the the mouse clicking of the scrollbar. **Update:** Just an OT update that with [`command` list from the Settings Schema](https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md), I was able to add the keybindings from scrolling (note that `scrollUp` scrolls a _line_ up and `scrollUpPage` scrolls a _page_ up; same from scrolling down): ```json { "command": "scrollDownPage", "keys": [ "shift+pgdn" ] }, { "command": "scrollUpPage", "keys": [ "shift+pgup" ] } ```

claunia commented

@wolf99 commented on GitHub (Mar 19, 2020):

Doesn't work for me either.

Terminal 0.10.761.0
Windows: 1909 (18363.720)

This hasn't worked for me since I first installed WT last year. Mouse wheel scrolling hasn't worked either (haven't tried that with the 0.10 release yet though), is there a separate issue for mouse wheel scrolling or should that be covered here also?

@wolf99 commented on GitHub (Mar 19, 2020): Doesn't work for me either. Terminal 0.10.761.0 Windows: 1909 (18363.720) This hasn't worked for me since I first installed WT last year. Mouse wheel scrolling hasn't worked either (haven't tried that with the 0.10 release yet though), is there a separate issue for mouse wheel scrolling or should that be covered here also?

claunia commented

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

@wolf99 I'm sure that there's another issue that's tracking the mouse scrolling not working, but this one isn't it. I fortunately have a personal HP laptop that repros this bug with it's touchpad, so I'm going to be using that to debug and investigate. However, I'd doubt that this investigation would also apply to all mouse devices. I don't want you thinking that resolving this issue will also fix your mouse issue.

@zadjii-msft commented on GitHub (Mar 19, 2020): @wolf99 I'm _sure_ that there's another issue that's tracking the mouse scrolling not working, but this one isn't it. I fortunately have a personal HP laptop that repros this bug with it's touchpad, so I'm going to be using that to debug and investigate. However, I'd doubt that this investigation would also apply to all mouse devices. I don't want you thinking that resolving _this_ issue will _also_ fix your mouse issue.

claunia commented

@wolf99 commented on GitHub (Mar 19, 2020):

@zadjii-msft Just tried 0.10 release with mouse, it's working now! 😄
Glad you're able to repro the track pad issue as it is affecting a lot of people by the look of this issue.

@wolf99 commented on GitHub (Mar 19, 2020): @zadjii-msft Just tried 0.10 release with mouse, it's working now! 😄 Glad you're able to repro the track pad issue as it is affecting a lot of people by the look of this issue.

claunia commented

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

Oh no this is horrifying.

This might not apply super broadly, but this is what I've found with my investigation this morning. I've got a HP Spectre 2017 x360 that I use at home, with a touchpad using the synaptics drivers.

From what I can tell, the Synaptics touchpads don't support "Scroll inactive windows" at all. notepad.exe, the Settings app, nothing. Even with "Scroll inactive windows when I hover over them" enabled.

I'm positive that the trackpad is the problem here, because using an external mouse works fine for both scrolling inactive windows and the Terminal on this laptop.

Turns out, this is a very broad problem. Even info from 3 years ago points at solutions that are decades old (and not verified).

What does this have to do with the Terminal?

As it turns out, XAML Islands, which we're using to host our XAML content (read: the entire UI), uses an inactive HWND to host the XAML content. So we're never even getting the mouse events in TermControl::_MouseScrollHandler. This issue is more specifically being tracked by https://github.com/microsoft/terminal/issues/2606 and https://github.com/microsoft/microsoft-ui-xaml/issues/2101. I'm betting that this is also going to be the root cause of this issue here.

I'm going to investigate if our root HWND gets the trackpad scrolling events that the XAML Island is ignoring. Maybe I can manually forward them to the XAML island somehow? I'm not overly optimistic at this point.

/cc @Austin-Lamb @ocalvo

@zadjii-msft commented on GitHub (Mar 24, 2020): Oh no this is horrifying. This might not apply super broadly, but this is what I've found with my investigation this morning. I've got a HP Spectre 2017 x360 that I use at home, with a touchpad using the synaptics drivers. From what I can tell, the Synaptics touchpads don't support "Scroll inactive windows" _at all_. `notepad.exe`, the Settings app, nothing. Even with "Scroll inactive windows when I hover over them" enabled. ![image](https://user-images.githubusercontent.com/18356694/77447498-be77f300-6dbd-11ea-941c-06697b59f4f5.png) I'm positive that the trackpad is the problem here, because using an external mouse works fine for both scrolling inactive windows and the Terminal on this laptop. Turns out, this is a [very broad problem](https://www.google.com/search?client=firefox-b-1-d&q=synaptics+inactive+window). Even info from [3 years ago](https://superuser.com/questions/1127755/scroll-inactive-windows-when-i-hover-over-them-not-working-with-every-applicat) points at solutions that are decades old (and not verified). What does this have to do with the Terminal? As it turns out, XAML Islands, which we're using to host our XAML content (read: the entire UI), uses an _inactive_ HWND to host the XAML content. So we're never even getting the mouse events in `TermControl::_MouseScrollHandler`. This issue is more specifically being tracked by https://github.com/microsoft/terminal/issues/2606 and https://github.com/microsoft/microsoft-ui-xaml/issues/2101. I'm betting that this is also going to be the root cause of this issue here. I'm going to investigate if our root HWND gets the trackpad scrolling events that the XAML Island is ignoring. Maybe I can manually forward them to the XAML island somehow? I'm not overly optimistic at this point. /cc @Austin-Lamb @ocalvo

claunia commented

@pamtbaau commented on GitHub (Mar 24, 2020):

@zadjii-msft, I'm using a Lenovo B590 using Synaptics Touchpad v7.5 drivers.

notepad.exe scrolls fine. In fact, every app scrolls fine, except Microsoft Terminal...

Any other app you would like me to test?

@pamtbaau commented on GitHub (Mar 24, 2020): @zadjii-msft, I'm using a Lenovo B590 using Synaptics Touchpad v7.5 drivers. notepad.exe scrolls fine. In fact, every app scrolls fine, except Microsoft Terminal... Any other app you would like me to test?

claunia commented

@Uxorious commented on GitHub (Mar 24, 2020):

FYI: A few releases back, it started working for me on an HP Spectre x360 with Synaptics drivers.
I can also scroll background/inactive windows.

@Uxorious commented on GitHub (Mar 24, 2020): FYI: A few releases back, it started working for me on an HP Spectre x360 with Synaptics drivers. I can also scroll background/inactive windows.

claunia commented

@dkter commented on GitHub (Mar 24, 2020):

@pamtbaau

notepad.exe scrolls fine.

does it scroll when you have another window in the foreground? (i.e. open two windows side by side, then try to scroll the inactive one.)

@dkter commented on GitHub (Mar 24, 2020): @pamtbaau > notepad.exe scrolls fine. does it scroll when you have another window in the foreground? (i.e. open two windows side by side, then try to scroll the inactive one.)

claunia commented

@pamtbaau commented on GitHub (Mar 24, 2020):

@dkter, @zadjii-msft 🤦‍♂ You're right, it doesn't work...

@pamtbaau commented on GitHub (Mar 24, 2020): @dkter, @zadjii-msft 🤦‍♂ You're right, it doesn't work...

claunia commented

@Uxorious commented on GitHub (Mar 24, 2020):

Huh that is really interesting.
For me it works sometimes - but it depends on what the FOREGROUND app is.

For example, I tried it earlier with Outlook in the foreground and Notepad in the background.
That worked.

But when I received this last mail, I tried it again. This time with Chrome/Gmail in the foreground.
This does NOT work.

@Uxorious commented on GitHub (Mar 24, 2020): Huh that is really interesting. For me it works sometimes - but it depends on what the FOREGROUND app is. For example, I tried it earlier with Outlook in the foreground and Notepad in the background. That worked. But when I received this last mail, I tried it again. This time with Chrome/Gmail in the foreground. This does NOT work.

claunia commented

@msbrunoalves commented on GitHub (Mar 24, 2020):

Oh no this is horrifying.

This might not apply super broadly, but this is what I've found with my investigation this morning. I've got a HP Spectre 2017 x360 that I use at home, with a touchpad using the synaptics drivers.

From what I can tell, the Synaptics touchpads don't support "Scroll inactive windows" at all. notepad.exe, the Settings app, nothing. Even with "Scroll inactive windows when I hover over them" enabled.

I'm positive that the trackpad is the problem here, because using an external mouse works fine for both scrolling inactive windows and the Terminal on this laptop.

Turns out, this is a very broad problem. Even info from 3 years ago points at solutions that are decades old (and not verified).

What does this have to do with the Terminal?

As it turns out, XAML Islands, which we're using to host our XAML content (read: the entire UI), uses an inactive HWND to host the XAML content. So we're never even getting the mouse events in TermControl::_MouseScrollHandler. This issue is more specifically being tracked by #2606 and microsoft/microsoft-ui-xaml#2101. I'm betting that this is also going to be the root cause of this issue here.

I'm going to investigate if our root HWND gets the trackpad scrolling events that the XAML Island is ignoring. Maybe I can manually forward them to the XAML island somehow? I'm not overly optimistic at this point.

/cc @Austin-Lamb @ocalvo

That probably explains why scroll doesn't work with VMWare or Virtualbox either

@msbrunoalves commented on GitHub (Mar 24, 2020): > > > Oh no this is horrifying. > > This might not apply super broadly, but this is what I've found with my investigation this morning. I've got a HP Spectre 2017 x360 that I use at home, with a touchpad using the synaptics drivers. > > From what I can tell, the Synaptics touchpads don't support "Scroll inactive windows" _at all_. `notepad.exe`, the Settings app, nothing. Even with "Scroll inactive windows when I hover over them" enabled. > ![image](https://user-images.githubusercontent.com/18356694/77447498-be77f300-6dbd-11ea-941c-06697b59f4f5.png) > I'm positive that the trackpad is the problem here, because using an external mouse works fine for both scrolling inactive windows and the Terminal on this laptop. > > Turns out, this is a [very broad problem](https://www.google.com/search?client=firefox-b-1-d&q=synaptics+inactive+window). Even info from [3 years ago](https://superuser.com/questions/1127755/scroll-inactive-windows-when-i-hover-over-them-not-working-with-every-applicat) points at solutions that are decades old (and not verified). > > What does this have to do with the Terminal? > > As it turns out, XAML Islands, which we're using to host our XAML content (read: the entire UI), uses an _inactive_ HWND to host the XAML content. So we're never even getting the mouse events in `TermControl::_MouseScrollHandler`. This issue is more specifically being tracked by #2606 and [microsoft/microsoft-ui-xaml#2101](https://github.com/microsoft/microsoft-ui-xaml/issues/2101). I'm betting that this is also going to be the root cause of this issue here. > > I'm going to investigate if our root HWND gets the trackpad scrolling events that the XAML Island is ignoring. Maybe I can manually forward them to the XAML island somehow? I'm not overly optimistic at this point. > > /cc @Austin-Lamb @ocalvo That probably explains why scroll doesn't work with VMWare or Virtualbox either

claunia commented

@mquevill commented on GitHub (Mar 25, 2020):

Huh that is really interesting.
For me it works sometimes - but it depends on what the FOREGROUND app is.

For example, I tried it earlier with Outlook in the foreground and Notepad in the background.
That worked.

But when I received this last mail, I tried it again. This time with Chrome/Gmail in the foreground.
This does NOT work.

I have the same behavior on my system. Scrolls fine with the touchpad while inactive when Settings is in the foreground; does not scroll when Chrome is in the foreground.

When the window is active, my touchpad will not scroll at all. Mouse wheel works fine (in all cases). But I have never run into issues with any other applications with my touchpad (granted, it's an older model).

Windows Terminal 0.10.781.0
Windows 10 Pro 1909 (18363.720)
Synaptics Driver 19.2.17.55

@mquevill commented on GitHub (Mar 25, 2020): > Huh that is really interesting. > For me it works sometimes - but it depends on what the FOREGROUND app is. > > For example, I tried it earlier with Outlook in the foreground and Notepad in the background. > That worked. > > But when I received this last mail, I tried it again. This time with Chrome/Gmail in the foreground. > This does NOT work. I have the same behavior on my system. Scrolls fine with the touchpad while inactive when Settings is in the foreground; does not scroll when Chrome is in the foreground. When the window is active, my touchpad will not scroll at all. Mouse wheel works fine (in all cases). But I have never run into issues with any other applications with my touchpad (granted, it's an older model). Windows Terminal 0.10.781.0 Windows 10 Pro 1909 (18363.720) Synaptics Driver 19.2.17.55

claunia commented

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

Thanks for the clarification everyone! It seems like on my machine, I can also repro this behavior where different foreground apps change whether an inactive window can be scrolled or not. This is an incredibly peculiar bug, which might be partially related to this. I'm still trying to work on a workaround, but we'll see if that's possible or not :/

@zadjii-msft commented on GitHub (Mar 25, 2020): Thanks for the clarification everyone! It seems like on my machine, I can also repro this behavior where different foreground apps change whether an inactive window can be scrolled or not. This is an incredibly peculiar bug, which might be partially related to this. I'm still trying to work on a workaround, but we'll see if that's possible or not :/

claunia commented

@Paul-Weisser commented on GitHub (Mar 25, 2020):

@zadjii-msft Just checked out the branch you referenced. Looks promising! Fixes this issue for me 👍

BTW: Props to your commit messages 🥇

@Paul-Weisser commented on GitHub (Mar 25, 2020): @zadjii-msft Just checked out the branch you referenced. Looks promising! Fixes this issue for me 👍 BTW: Props to your commit messages 🥇

claunia commented

@wolf99 commented on GitHub (Apr 1, 2020):

Props on the effort here @zadjii-msft !
I look forward to this landing on my machine 👨‍💻

@wolf99 commented on GitHub (Apr 1, 2020): Props on the effort here @zadjii-msft ! I look forward to this landing on my machine 👨‍💻

claunia commented

@ghost commented on GitHub (Apr 22, 2020):

:tada:This issue was addressed in #5131, which has now been successfully released as Windows Terminal Preview v0.11.1121.0.🎉

Handy links:

@ghost commented on GitHub (Apr 22, 2020): :tada:This issue was addressed in #5131, which has now been successfully released as `Windows Terminal Preview v0.11.1121.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.11.1121.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)

claunia commented