starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

four finger custom gesture on touchpad #18268

New Issue
Closed
opened 2026-01-31 06:08:42 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 06:08:42 +00:00
Owner
Copy Link

Originally created by @williamohara on GitHub (Aug 23, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044 Build 19044

Other Software

No response

Steps to reproduce

define a custom four fingered gesture to open up the start menu (taping windows key) by moving four fingers on touchpad up or down in settings->devices->touchpad->Advanced Gesture Configuration

image

Open WSL distro in a terminal tab
or - focus on current open tab (making it the active window)
try the four-finger gesture
notice that it doesn't work

Expected Behavior

I expect the four finger gesture to work when terminal is the active window

Actual Behavior

four finger custom gestures do not work when terminal is the active window

Originally created by @williamohara on GitHub (Aug 23, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044 Build 19044 ### Other Software _No response_ ### Steps to reproduce define a custom four fingered gesture to open up the start menu (taping windows key) by moving four fingers on touchpad up or down in `settings->devices->touchpad->Advanced Gesture Configuration` ![image](https://user-images.githubusercontent.com/17223014/186040565-7b2563dc-4d29-4030-9d8f-be850955ae40.png) Open WSL distro in a terminal tab or - focus on current open tab (making it the active window) try the four-finger gesture notice that it doesn't work ### Expected Behavior I expect the four finger gesture to work when terminal is the active window ### Actual Behavior four finger custom gestures do not work when terminal is the active window
claunia commented 2026-01-31 06:08:44 +00:00
Author
Owner
Copy Link

@williamohara commented on GitHub (Aug 23, 2022):

I notice the same behavior when VS Code is the active window and when any virtualized machine is the active window (i.e. not using terminal) and when I have windows power shell open too.

I do not notice the behavior when I have the CMD open - but when i have command prompt open in Windows Terminal the behavior manifests itself

@williamohara commented on GitHub (Aug 23, 2022): I notice the same behavior when VS Code is the active window and when any virtualized machine is the active window (i.e. not using terminal) and when I have windows power shell open too. I do not notice the behavior when I have the CMD open - but when i have command prompt open in Windows Terminal the behavior manifests itself
claunia commented 2026-01-31 06:08:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

when I have windows power shell open too

wait what? Powershell and CMD both run in the vintage console conhost - powershell shouldn't be able to do anything with the conhost window to differentiate it from CMD in this regard...

@zadjii-msft commented on GitHub (Aug 23, 2022): > when I have windows power shell open too wait _what_? Powershell and CMD both run in the vintage console conhost - powershell shouldn't be able to do anything with the conhost window to differentiate it from CMD in this regard...
claunia commented 2026-01-31 06:08:44 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 29, 2023):

Hi @williamohara. Does this happen on Windows 11? How about with the latest version of Windows Terminal? We weren't able to reproduce this on Win 11 with our selfhosted version. Thanks in advance.

@carlos-zamora commented on GitHub (Mar 29, 2023): Hi @williamohara. Does this happen on Windows 11? How about with the latest version of Windows Terminal? We weren't able to reproduce this on Win 11 with our selfhosted version. Thanks in advance.
claunia commented 2026-01-31 06:08:45 +00:00
Author
Owner
Copy Link

@williamohara commented on GitHub (Mar 29, 2023):

Hi @carlos-zamora

yes, I have both Windows 10 and Windows 11 and I have the exact same issue on both. Could it be the combo of using a 4 finger gesture assigned to a windows key?

let me know if you need system info or something...

@williamohara commented on GitHub (Mar 29, 2023): Hi @carlos-zamora yes, I have both Windows 10 and Windows 11 and I have the exact same issue on both. Could it be the combo of using a 4 finger gesture assigned to a windows key? let me know if you need system info or something...
claunia commented 2026-01-31 06:08:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 30, 2023):

That's wacky. I just tried to repro this on my surface laptop and couldn't. Everything worked as I'd expect.

What kind of trackpad driver do you have? I know there's been issues with certain drivers and XAML Islands in the past, maybe this is something like that.

I suppose another thing to test would be trying to bind the gesture to just like, a or something, and seeing if the a shows up in the Terminal or not. Maybe something's eating it?

@zadjii-msft commented on GitHub (Mar 30, 2023): That's wacky. I just tried to repro this on my surface laptop and couldn't. Everything worked as I'd expect. What kind of trackpad driver do you have? I know there's been issues with certain drivers and XAML Islands in the past, maybe this is something like that. I suppose another thing to test would be trying to bind the gesture to just like, <kbd>a</kbd> or something, and seeing if the `a` shows up in the Terminal or not. Maybe something's eating it?
claunia commented 2026-01-31 06:08:45 +00:00
Author
Owner
Copy Link

@williamohara commented on GitHub (Apr 4, 2023):

My Laptop is a Lenovo Yoga has a touchpad using a Microsoft HID Compliant Mouse Driver 10.0.22621.1. I have an apple trackpad attached to it via USB along with this https://github.com/imbushuo/mac-precision-touchpad. The Lenovo touchpad did not work before I installed the Apple precision touchpad implementation from the repo. (I tried it right after a fresh installation of Windows 11)

My Win10 PC has the exact same Apple Precision Touchpad implementation from https://github.com/imbushuo/mac-precision-touchpad. also using the Microsoft HID Compliant Mouse Driver 10.0.22621.1

I tried setting it to type a and swiped up three times in the terminal - nothing - I then alt-tabbed back to my browser and tried again - below are the results.
aaa

@williamohara commented on GitHub (Apr 4, 2023): My Laptop is a Lenovo Yoga has a touchpad using a Microsoft HID Compliant Mouse Driver 10.0.22621.1. I have an apple trackpad attached to it via USB along with this https://github.com/imbushuo/mac-precision-touchpad. The Lenovo touchpad did not work before I installed the Apple precision touchpad implementation from the repo. (I tried it right after a fresh installation of Windows 11) My Win10 PC has the exact same Apple Precision Touchpad implementation from https://github.com/imbushuo/mac-precision-touchpad. also using the Microsoft HID Compliant Mouse Driver 10.0.22621.1 I tried setting it to type a and swiped up three times in the terminal - nothing - I then alt-tabbed back to my browser and tried again - below are the results. aaa
claunia commented 2026-01-31 06:08:45 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 5, 2023):

Thanks for getting back to us. We suspect this may be a XAML Islands bug. Do you mind testing the repro out with c:\windows\system32\PerceptionSimulation\PerceptionSimulationInput.exe instead of Windows Terminal? If it repros, then that kinda confirms our suspicion.

@carlos-zamora commented on GitHub (Apr 5, 2023): Thanks for getting back to us. We suspect this may be a XAML Islands bug. Do you mind testing the repro out with c:\windows\system32\PerceptionSimulation\PerceptionSimulationInput.exe instead of Windows Terminal? If it repros, then that kinda confirms our suspicion.
claunia commented 2026-01-31 06:08:46 +00:00
Author
Owner
Copy Link

@williamohara commented on GitHub (Apr 6, 2023):

I started c:\windows\system32\PerceptionSimulation\PerceptionSimulationInput.exe and tried a few things

I turned "Connect to a remote device" off

When I use these settings, the custom Up and down four finger gestures do not work when the Perception Simulator is the active window:
Left Controller: On
Use keyboard for simulation - on
Use Mouse for simulation - on
Use Gamepad for simulation on

but when I use these settings, the custom Up and down four finger gestures work when the Perception Simulator is the active window:
Left Controller: On
Use keyboard for simulation - off
Use Mouse for simulation - on
Use Gamepad for simulation on

@williamohara commented on GitHub (Apr 6, 2023): I started c:\windows\system32\PerceptionSimulation\PerceptionSimulationInput.exe and tried a few things I turned "Connect to a remote device" off When I use these settings, the custom Up and down four finger gestures _do not work_ when the Perception Simulator is the active window: Left Controller: On Use keyboard for simulation - on Use Mouse for simulation - on Use Gamepad for simulation on but when I use these settings, the custom Up and down four finger gestures _work_ when the Perception Simulator is the active window: Left Controller: On Use keyboard for simulation - _off_ Use Mouse for simulation - on Use Gamepad for simulation on
claunia commented 2026-01-31 06:08:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 6, 2023):

Well, that's really unexpected. We were using Perception Simulator as a test app because it has the same UI characteristics as Terminal, not because we thought any of the settings inside it would change the repro.

I wonder if there's some sort of control focus issue here? I wonder if we need a simpler repro app...

@DHowett commented on GitHub (Apr 6, 2023): _Well, that's really unexpected._ We were using Perception Simulator as a test app because it has the same UI characteristics as Terminal, not because we thought any of the settings inside it would change the repro. I wonder if there's some sort of control focus issue here? I wonder if we need a simpler repro app...
claunia commented 2026-01-31 06:08:46 +00:00
Author
Owner
Copy Link

@williamohara commented on GitHub (Apr 9, 2023):

I found something else. It made no sense that when you guys tested, it worked as expected and when I do it, it did not work. So ,I looked at the initial bug report and I thought of all the things that I may not have described, and I found one.

  1. I am running the Tabs "As an Administrator".
  2. When I turn off the "Run this profile as an administrator" the custom four finger gesture works!!!
  3. I am also running My Visual Studio Code "As an Administrator" and my Windows Power Shell terminal "As an Administrator"
  4. I had initially reported that the CMD Prompt Window did not suffer the problem - but I wasn't running it "As an Administrator" - I tried doing so.... and I get same results! Running as Administrator disabled custom four finger gestures.
  5. I tried "non-terminal" software too. I tried running Microsoft Word "As an Administrator" and the custom four finger gesture does not work. Running normally - it does work.

So, this may not have something to do with the Terminal application at all - it has something to do with how windows manages control of windows. Specifically, windows running applications As an Administrator.

Moreover, it may not have anything to do with four finger gestures in general - just the specific one I have set up (opening the start menu). I am thinking too that this may not be something one can fix either, not easily at least. Why? Because I also notice when I use the four finger gesture the active window loses focus (my window boarder changes) so the start menu comes on top and is active. Then when I close the start menu - the last window that was active before opening start reactivates. I am thinking that this whole problem is because of a security requirement conflict - because the start menu needs to refocus the last window. - If this were done with Apps Running as an administrator - that would give non-administrator elevated apps an avenue to control admin apps.

So whatever bit of software in windows is handling custom gestures - may need to have elevated access.

@williamohara commented on GitHub (Apr 9, 2023): I found something else. It made no sense that when you guys tested, it worked as expected and when I do it, it did not work. So ,I looked at the initial bug report and I thought of all the things that I may not have described, and I found one. 1. I am running the Tabs "As an Administrator". 2. When I turn off the "Run this profile as an administrator" the custom four finger gesture works!!! 3. I am also running My Visual Studio Code "As an Administrator" and my Windows Power Shell terminal "As an Administrator" 4. I had initially reported that the CMD Prompt Window did not suffer the problem - but I wasn't running it "As an Administrator" - I tried doing so.... and I get same results! Running as Administrator disabled custom four finger gestures. 5. I tried "non-terminal" software too. I tried running Microsoft Word "As an Administrator" and the custom four finger gesture does not work. Running normally - it does work. So, this may not have something to do with the Terminal application at all - it has something to do with how windows manages control of windows. Specifically, windows running applications As an Administrator. Moreover, it may not have anything to do with four finger gestures in general - just the specific one I have set up (opening the start menu). I am thinking too that this may not be something one can fix either, not easily at least. Why? Because I also notice when I use the four finger gesture the active window loses focus (my window boarder changes) so the start menu comes on top and is active. Then when I close the start menu - the last window that was active before opening start reactivates. I am thinking that this whole problem is because of a security requirement conflict - because the start menu needs to refocus the last window. - If this were done with Apps Running as an administrator - that would give non-administrator elevated apps an avenue to control admin apps. So whatever bit of software in windows is handling custom gestures - may need to have elevated access.
claunia commented 2026-01-31 06:08:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 3, 2023):

(assigning myself to make sure I get the right area path to file feedback on)

@zadjii-msft commented on GitHub (May 3, 2023): (assigning myself to make sure I get the right area path to file feedback on)
claunia commented 2026-01-31 06:08:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 4, 2023):

Okay, so this is definitely out of our hands. I filed MSFT:44518206 internally to track. I'll post if there are updates on that thread.

I'm gonna close this out though, since I don't believe there's anything else for us (the Terminal team) to do here. Thanks!

@zadjii-msft commented on GitHub (May 4, 2023): Okay, so this is definitely out of our hands. I filed MSFT:44518206 internally to track. I'll post if there are updates on that thread. I'm gonna close this out though, since I don't believe there's anything else for _us_ (the Terminal team) to do here. Thanks!
claunia commented 2026-01-31 06:08:47 +00:00
Author
Owner
Copy Link

@zwalden commented on GitHub (Oct 9, 2024):

So... what's the status? This is definitely still a problem on windows 10... @zadjii-msft

@zwalden commented on GitHub (Oct 9, 2024): So... what's the status? This is definitely still a problem on windows 10... @zadjii-msft
claunia commented 2026-01-31 06:08:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 9, 2024):

It's still open on the input team, on their backlog. Nothing new to report.

@zadjii-msft commented on GitHub (Oct 9, 2024): It's still open on the input team, on their backlog. Nothing new to report.
claunia commented 2026-01-31 06:08:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 16, 2024):

@zwalden I see you in my emails posting then deleting comments, so I'll reply here anyways:

I tried "non-terminal" software too. I tried running Microsoft Word "As an Administrator" and the custom four finger gesture does not work. Running normally - it does work.

That right there is evidence that this is not an issue unique to the Terminal. This is a broader issue with custom gestures and elevated applications. Because it's not something unique to our codebase, I filed an issue on the team that owns custom gestures. I closed this issue as "not planned", since our team, the Terminal team, is not planning on doing any work to resolve this ourselves.

This is where we tread the annoying line of "issue tracking is not exactly work tracking". There is a bug here, yes, but we also use our list of issues as a work backlog, and this isn't something for our team to work on anymore. Sorry for any confusion!

@zadjii-msft commented on GitHub (Dec 16, 2024): @zwalden I see you in my emails posting then deleting comments, so I'll reply here anyways: > I tried "non-terminal" software too. I tried running Microsoft Word "As an Administrator" and the custom four finger gesture does not work. Running normally - it does work. That right there is evidence that this is _not_ an issue unique to the Terminal. This is a broader issue with custom gestures and elevated applications. Because it's not something unique to our codebase, I filed an issue on the team that owns custom gestures. I closed **this** issue as "not planned", since our team, the Terminal team, is not planning on doing any work to resolve this ourselves. This is where we tread the annoying line of "issue tracking is not exactly work tracking". There is a bug here, yes, but we also use our list of issues as a work backlog, and this isn't something for our team to work on anymore. Sorry for any confusion!
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-Input Issue-Bug Priority-3 Product-Terminal Resolution-External 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#18268
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?