starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Arrow keys not working on Touchscreen (on-screen) keyboard #10435

New Issue
Closed
opened 2026-01-31 02:21:27 +00:00 by claunia · 22 comments
claunia commented 2026-01-31 02:21:27 +00:00
Owner
Copy Link

Originally created by @joscdk on GitHub (Sep 1, 2020).

Environment

Windows build number: 10.0.20201.0
Windows Terminal version (if applicable): 1.3.2382.0

Steps to reproduce

  1. Open Windows Terminal Pre release on a computer with touch screen.
  2. Popup the "on-screen" keyboard
  3. Set the keyboard to "full size", to get arrow keys
  4. Enter a command, try to click arrow left/right
  5. Run the command and click up

This is tested both in PowerShell and WSL 2 through Windows Terminal

Expected behavior

I would expect the arrow keys to work, for example for going back in command history, or to use arrow keys in Vim or similar.

Actual behavior

The arrow keys is not working, nothing happens when you click them. You can try to open e.g. Windows PowerShell directly, where it will work.

Originally created by @joscdk on GitHub (Sep 1, 2020). # Environment ```none Windows build number: 10.0.20201.0 Windows Terminal version (if applicable): 1.3.2382.0 ``` # Steps to reproduce 1. Open Windows Terminal Pre release on a computer with touch screen. 2. Popup the "on-screen" keyboard 3. Set the keyboard to "full size", to get arrow keys 4. Enter a command, try to click arrow left/right 5. Run the command and click up This is tested both in PowerShell and WSL 2 through Windows Terminal # Expected behavior I would expect the arrow keys to work, for example for going back in command history, or to use arrow keys in Vim or similar. # Actual behavior The arrow keys is not working, nothing happens when you click them. You can try to open e.g. Windows PowerShell directly, where it will work.
claunia commented 2026-01-31 02:21:29 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 1, 2020):

FWIW, the arrow keys on the on-screen keyboard work fine for me. I'm using the same terminal version as you, but I'm still on Windows build 10.0.18362.959 (I doubt that makes any difference though).

This might be a bit difficult to do if you only have the on-screen keyboard, but can you try holding down both Alt keys when opening a new tab - that should give you an extra debug pane that shows the input/output control sequences seen by the terminal. If you can get that working, see what shows up in that debug view when pressing the arrow keys.

@j4james commented on GitHub (Sep 1, 2020): FWIW, the arrow keys on the on-screen keyboard work fine for me. I'm using the same terminal version as you, but I'm still on Windows build 10.0.18362.959 (I doubt that makes any difference though). This might be a bit difficult to do if you only have the on-screen keyboard, but can you try holding down both <kbd>Alt</kbd> keys when opening a new tab - that should give you an extra debug pane that shows the input/output control sequences seen by the terminal. If you can get that working, see what shows up in that debug view when pressing the arrow keys.
claunia commented 2026-01-31 02:21:29 +00:00
Author
Owner
Copy Link

@joscdk commented on GitHub (Sep 1, 2020):

@j4james hmm think you might have a point regarding the Windows version actually. I just tried the same on another machine running the same version of Windows, it still didn't work.
I then tried on my work laptop, running an older version of Windows 10 (19042.487) there the touch keyboard worked fine with arrow keys.

However on the newer windows versions, it works in PowerShell plain and not in Windows Terminal, so still think the issue is somewhere here, but at least it narrowed it down a bit.

I tried holding down both Alt keys, and it just opened a new pane, and not a new tab (no debug settings), is there another way to get the debug info, so i can try providing some more details? (Tried taking the default settings and still the same).

@joscdk commented on GitHub (Sep 1, 2020): @j4james hmm think you might have a point regarding the Windows version actually. I just tried the same on another machine running the same version of Windows, it still didn't work. I then tried on my work laptop, running an older version of Windows 10 (19042.487) there the touch keyboard worked fine with arrow keys. However on the newer windows versions, it works in PowerShell plain and not in Windows Terminal, so still think the issue is somewhere here, but at least it narrowed it down a bit. I tried holding down both Alt keys, and it just opened a new pane, and not a new tab (no debug settings), is there another way to get the debug info, so i can try providing some more details? (Tried taking the default settings and still the same).
claunia commented 2026-01-31 02:21:29 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

Oh, you will need to set the global setting debugFeaturesEnabled to true for the double-Alt thing to work. Sorry about that 😅

@DHowett commented on GitHub (Sep 3, 2020): Oh, you will need to set the global setting `debugFeaturesEnabled` to `true` for the double-Alt thing to work. Sorry about that 😅
claunia commented 2026-01-31 02:21:30 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 7, 2020):

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 (Sep 7, 2020): 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 2026-01-31 02:21:30 +00:00
Author
Owner
Copy Link

@codeman38 commented on GitHub (Sep 7, 2020):

I'm also experiencing this issue on Windows 10 19041.450 - the arrow keys and Delete key in the on-screen keyboard seem to do nothing in Terminal version 1.2.2381.0.

Holding down both Alt keys on my physical keyboard while opening a tab just opens a new pane in the current tab, even if I've added "debugFeaturesEnabled": true to my config.

Edit: Same result under Terminal Preview 1.3.2382.0 as well - arrow keys on onscreen keyboard don't work, and holding both Alt keys on the physical keyboard while opening a tab just opens a new pane.

@codeman38 commented on GitHub (Sep 7, 2020): I'm also experiencing this issue on Windows 10 19041.450 - the arrow keys and Delete key in the on-screen keyboard seem to do nothing in Terminal version 1.2.2381.0. Holding down both Alt keys on my physical keyboard while opening a tab just opens a new pane in the current tab, even if I've added `"debugFeaturesEnabled": true` to my config. **Edit:** Same result under Terminal Preview 1.3.2382.0 as well - arrow keys on onscreen keyboard don't work, and holding both Alt keys on the physical keyboard while opening a tab just opens a new pane.
claunia commented 2026-01-31 02:21:31 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 7, 2020):

I just checked my settings now, and I think it's actually meant to be "debugFeatures": true. Sorry about the confusion.

@j4james commented on GitHub (Sep 7, 2020): I just checked my settings now, and I think it's actually meant to be `"debugFeatures": true`. Sorry about the confusion.
claunia commented 2026-01-31 02:21:32 +00:00
Author
Owner
Copy Link

@joscdk commented on GitHub (Sep 7, 2020):

@j4james oh perfect, that worked. When i generally press the onboard keyboard, debug data is printed out. However when i press the arrow keys, nothing is printed. Based on what @codeman38 was writing, the same thing happens when clicking "Delete".

If you want a screen recording of it, just say so :)

@joscdk commented on GitHub (Sep 7, 2020): @j4james oh perfect, that worked. When i generally press the onboard keyboard, debug data is printed out. However when i press the arrow keys, nothing is printed. Based on what @codeman38 was writing, the same thing happens when clicking "Delete". If you want a screen recording of it, just say so :)
claunia commented 2026-01-31 02:21:32 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 8, 2020):

Thanks for the info. I don't think the screen recording will be necessary. I'm not sure what the problem is, though. It sounds like we might not be receiving keyboard events for those keys which would be weird. Hopefully one of the core devs will have a better idea of what is going wrong.

@j4james commented on GitHub (Sep 8, 2020): Thanks for the info. I don't think the screen recording will be necessary. I'm not sure what the problem is, though. It sounds like we might not be receiving keyboard events for those keys which would be weird. Hopefully one of the core devs will have a better idea of what is going wrong.
claunia commented 2026-01-31 02:21:33 +00:00
Author
Owner
Copy Link

@Alovchin91 commented on GitHub (Sep 9, 2020):

Got the same problem with arrow keys on my Surface Pro X.

Windows version: 10.0.19041.508
Terminal version: 1.2.2381.0 (Microsoft Store)

@Alovchin91 commented on GitHub (Sep 9, 2020): Got the same problem with arrow keys on my Surface Pro X. Windows version: 10.0.19041.508 Terminal version: 1.2.2381.0 (Microsoft Store)
claunia commented 2026-01-31 02:21:34 +00:00
Author
Owner
Copy Link

@AJFirewolf commented on GitHub (Sep 12, 2020):

Experiencing the same issue on my Surface Pro 7. On-screen arrow and delete keys do not respond in Windows Terminal. They behave as expected in other programs including native PowerShell and CMD.
Windows Terminal Version: 1.2.2381.0
Windows 10 Home 19041.508

@AJFirewolf commented on GitHub (Sep 12, 2020): Experiencing the same issue on my Surface Pro 7. On-screen arrow and delete keys do not respond in Windows Terminal. They behave as expected in other programs including native PowerShell and CMD. Windows Terminal Version: 1.2.2381.0 Windows 10 Home 19041.508
claunia commented 2026-01-31 02:21:34 +00:00
Author
Owner
Copy Link

@MohsenFayyaz89 commented on GitHub (Sep 12, 2020):

Same here with Surface Pro 7, the on-screen arrow, and delete keys don't respond.

Windows 10 Home 18363,1082
Windows Terminal: 1.2.2381.0

@MohsenFayyaz89 commented on GitHub (Sep 12, 2020): Same here with Surface Pro 7, the on-screen arrow, and delete keys don't respond. Windows 10 Home 18363,1082 Windows Terminal: 1.2.2381.0
claunia commented 2026-01-31 02:21:35 +00:00
Author
Owner
Copy Link

@codeman38 commented on GitHub (Sep 14, 2020):

Wondering whether #7438 (failure with virtual arrow keys via keyboard remapping) might be related to this - it feels extremely similar, and seems to have started failing around the same time.

@codeman38 commented on GitHub (Sep 14, 2020): Wondering whether #7438 (failure with virtual arrow keys via keyboard remapping) might be related to this - it feels extremely similar, and seems to have started failing around the same time.
claunia commented 2026-01-31 02:21:35 +00:00
Author
Owner
Copy Link

@itskenny0 commented on GitHub (Sep 18, 2020):

Same issue on my Lumia 950 XL running WT 1.2.200825001-release1.2 on Windows 10 Pro 19041.488.

@itskenny0 commented on GitHub (Sep 18, 2020): Same issue on my Lumia 950 XL running WT 1.2.200825001-release1.2 on Windows 10 Pro 19041.488.
claunia commented 2026-01-31 02:21:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 18, 2020):

on my Lumia 950 XL running WT

image

image

@zadjii-msft commented on GitHub (Sep 18, 2020): > on my Lumia 950 XL running WT ![image](https://user-images.githubusercontent.com/18356694/93620756-217ac900-f9a0-11ea-838f-7970832cd715.png) ![image](https://user-images.githubusercontent.com/18356694/93620789-2ccdf480-f9a0-11ea-8a85-d23af7f581ac.png)
claunia commented 2026-01-31 02:21:35 +00:00
Author
Owner
Copy Link

@itskenny0 commented on GitHub (Sep 21, 2020):

@zadjii-msft https://github.com/WOA-Project/WOA-Deployer-Lumia
LumiaWoA

@itskenny0 commented on GitHub (Sep 21, 2020): @zadjii-msft https://github.com/WOA-Project/WOA-Deployer-Lumia ![LumiaWoA](https://i.ibb.co/JHWBnzD/6-EC48082-C2-BE-4-C6-E-93-C1-D7-EC0645-D1-E5.jpg)
claunia commented 2026-01-31 02:21:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2020):

Huh, this is super bizarre. I wonder if this only repros on devices without a physical keyboard. The on-screen keyboard works fine for me on 1.4.x, and 10.0.20222.1001, but I'm on a Surface Laptop.

I'll dig out my old surface pro 3 and see if that repros this.

@zadjii-msft commented on GitHub (Sep 29, 2020): Huh, this is super bizarre. I wonder if this only repros on devices without a physical keyboard. The on-screen keyboard works fine for me on 1.4.x, and 10.0.20222.1001, but I'm on a Surface Laptop. I'll dig out my old surface pro 3 and see if that repros this.
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@joscdk commented on GitHub (Sep 29, 2020):

@zadjii-msft even if i attach my keyboard to my surface go but uses the on-screen keyboard, it is the same :) .. I tried digging into the code, but didn't have enough free time to try debugging it unfortunately :/

@joscdk commented on GitHub (Sep 29, 2020): @zadjii-msft even if i attach my keyboard to my surface go but uses the on-screen keyboard, it is the same :) .. I tried digging into the code, but didn't have enough free time to try debugging it unfortunately :/
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 1, 2020):

Huh so I just tested this out, and it's the damnedest thing. The on screen keyboard works just fine on both my SP3 and slaptop. HOWEVER, the arrow keys on the touch keyboard on my SP3 don't work. I'm not sure how to get the touch keyboard to appear on my slaptop however.

@DHowett does someone on the team have a work surface pro that we could assign this bug to them? Is rather not try and install VS on that old SP3 lol.

My guess is the touch keyboard sends keys with scancode=0

@zadjii-msft commented on GitHub (Oct 1, 2020): Huh so I just tested this out, and it's the damnedest thing. The on screen keyboard works just fine on both my SP3 and slaptop. HOWEVER, the arrow keys on the _touch_ keyboard on my SP3 don't work. I'm not sure how to get the touch keyboard to appear on my slaptop however. @DHowett does someone on the team have a work surface pro that we could assign this bug to them? Is rather not try and install VS on that old SP3 lol. My guess is the touch keyboard sends keys with scancode=0
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 1, 2020):

Oh how ho, I found a way!

https://support.microsoft.com/en-us/help/4028719/windows-10-open-the-touch-keyboard#:~:text=Select%20the%20Touch%20keyboard%20icon,d%20like%20to%20enter%20text.&text=If%20you're%20not%20seeing,select%20Show%20touch%20keyboard%20button.

I can debug this on my slaptop now 😊

@zadjii-msft commented on GitHub (Oct 1, 2020): Oh how ho, I found a way! https://support.microsoft.com/en-us/help/4028719/windows-10-open-the-touch-keyboard#:~:text=Select%20the%20Touch%20keyboard%20icon,d%20like%20to%20enter%20text.&text=If%20you're%20not%20seeing,select%20Show%20touch%20keyboard%20button. I can debug this on my slaptop now 😊
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@2fst4u commented on GitHub (Oct 25, 2020):

Looks like you're already onto this but I'm just here after googling for a solution after my Surface Go's keyboard broke and I couldn't use my onscreen arrows 😂.

It would be awesome to get them working.

@2fst4u commented on GitHub (Oct 25, 2020): Looks like you're already onto this but I'm just here after googling for a solution after my Surface Go's keyboard broke and I couldn't use my onscreen arrows 😂. It would be awesome to get them working.
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2020):

:tada:This issue was addressed in #7900, which has now been successfully released as Windows Terminal v1.4.3141.0.🎉

Handy links:

@ghost commented on GitHub (Nov 11, 2020): :tada:This issue was addressed in #7900, which has now been successfully released as `Windows Terminal v1.4.3141.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.4.3141.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 02:21:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2020):

:tada:This issue was addressed in #7900, which has now been successfully released as Windows Terminal Preview v1.5.3142.0.🎉

Handy links:

@ghost commented on GitHub (Nov 11, 2020): :tada:This issue was addressed in #7900, which has now been successfully released as `Windows Terminal Preview v1.5.3142.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.3142.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Help Wanted Issue-Bug Priority-2 Product-Terminal Resolution-Fix-Committed
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#10435
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?