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

Tapping the + button with a touchscreen opens the menu rather than the default profile #19333

New Issue
Closed
opened 2026-01-31 06:40:24 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:40:24 +00:00
Owner
Copy Link

Originally created by @WillPittenger on GitHub (Feb 6, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

Edition Windows 11 Pro Version 22H2 Installed on ‎12-‎8-‎2022 OS build 22621.1194 Experience Windows Feature Experience Pack 1000.22638.1000.0

Other Software

PowerShell 7.3.2

Steps to reproduce

Using a touchscreen rather than a mouse, tap the + rather than the drop down menu.

Expected Behavior

WT should immediately open the default profile

Actual Behavior

WT opens the drop menu.

Originally created by @WillPittenger on GitHub (Feb 6, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number Edition Windows 11 Pro Version 22H2 Installed on ‎12-‎8-‎2022 OS build 22621.1194 Experience Windows Feature Experience Pack 1000.22638.1000.0 ### Other Software PowerShell 7.3.2 ### Steps to reproduce Using a touchscreen rather than a mouse, tap the + rather than the drop down menu. ### Expected Behavior WT should immediately open the default profile ### Actual Behavior WT opens the drop menu.
claunia added the Issue-BugResolution-External labels 2026-01-31 06:40:24 +00:00
claunia commented 2026-01-31 06:40:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 7, 2023):

Thanks for the report! This one is actually by design. The owners of the Windows UI controls have decided that the touch target for the + and the v are too small or too ambiguous, and that any tap on either of them should open the dropdown menu.

This behavior is conserved anywhere there's a dropdown combined with a button using the modern UI.

Notes from /duplicate https://github.com/microsoft/microsoft-ui-xaml/issues/178

This behavior is intentional because the chevron button is smaller than the recommended touch target size and would be too difficult to reliably hit, so touch tap always expands. I'll let adambarlow discuss whether in practice users like this behavior.

We have been having a few conversations about this and this while we haven't had negative end user feedback yet, we have had feedback from teams utilizing the control that it should work like mouse for touch.

It has not, as yet, been addressed. ☹️

@DHowett commented on GitHub (Feb 7, 2023): Thanks for the report! This one is actually by design. The owners of the Windows UI controls have decided that the touch target for the `+` and the `v` are too small or too ambiguous, and that any tap on _either_ of them should open the dropdown menu. This behavior is conserved anywhere there's a dropdown combined with a button using the modern UI. Notes from /duplicate https://github.com/microsoft/microsoft-ui-xaml/issues/178 > This behavior is intentional because the chevron button is smaller than the recommended touch target size and would be too difficult to reliably hit, so touch tap always expands. I'll let adambarlow discuss whether in practice users like this behavior. > We have been having a few conversations about this and this while we haven't had negative end user feedback yet, we have had feedback from teams utilizing the control that it should work like mouse for touch. It has not, as yet, been addressed. ☹️
claunia commented 2026-01-31 06:40:25 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 7, 2023):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 7, 2023): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
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 Issue-Bug Resolution-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#19333
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?