starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Window Terimal Preview - Tearout tab] : User is not able to perform the 'Tearout', 'Transfer' tab functionality using keyboard. #19687

New Issue
Closed
opened 2026-01-31 06:50:49 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:50:49 +00:00
Owner
Copy Link

Originally created by @Saiteja341 on GitHub (Apr 11, 2023).

Windows Terminal version

1.18.902.0

Windows build number

25324.1011

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 25324.1011)
App: Windows Terminal Preview
Screen Reader: Narrator

Steps to reproduce

Repro Steps:

1.Open Windows Terminal.
2.Open multiple 'Command prompt' using 'Ctrl + Shift + 1' keys.
3.Now try to perform 'Tearout' and 'Transfer' tab functionality using keyboard.
4.Observe the issue.

Users Experience:
Users who rely on keyboard will get impacted here & fail to use the functionality effectively.

Guideline link:
https://www.w3.org/TR/WCAG21/#keyboard

Attachments:
User is not able to perform the 'Tearout', 'Transfer' tab functionality using keyboard..zip

Expected Behavior

User should be able to perform the 'Tearout', 'Transfer' tab functionality using keyboard.

Even shortcut should be defined to perform 'Tearout', 'Transfer' tab- functionality.

Actual Behavior

User is not able to perform the 'Tearout', 'Transfer' tab functionality using keyboard.

Even no shortcut is defined for 'Tearout', 'Transfer' tab- functionality

Originally created by @Saiteja341 on GitHub (Apr 11, 2023). ### Windows Terminal version 1.18.902.0 ### Windows build number 25324.1011 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 25324.1011) App: Windows Terminal Preview Screen Reader: Narrator ### Steps to reproduce Repro Steps: 1.Open Windows Terminal. 2.Open multiple 'Command prompt' using 'Ctrl + Shift + 1' keys. 3.Now try to perform 'Tearout' and 'Transfer' tab functionality using keyboard. 4.Observe the issue. Users Experience: Users who rely on keyboard will get impacted here & fail to use the functionality effectively. Guideline link: https://www.w3.org/TR/WCAG21/#keyboard Attachments: [User is not able to perform the 'Tearout', 'Transfer' tab functionality using keyboard..zip](https://github.com/microsoft/terminal/files/11197147/User.is.not.able.to.perform.the.Tearout.Transfer.tab.functionality.using.keyboard.zip) ### Expected Behavior User should be able to perform the 'Tearout', 'Transfer' tab functionality using keyboard. > Even shortcut should be defined to perform 'Tearout', 'Transfer' tab- functionality. ### Actual Behavior User is not able to perform the 'Tearout', 'Transfer' tab functionality using keyboard. > Even no shortcut is defined for 'Tearout', 'Transfer' tab- functionality
claunia commented 2026-01-31 06:50:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 11, 2023):

@Saiteja341 The user is free to define actions like:


        { "keys": "f1", "command": { "action": "moveTab", "window": "1" }, },
        { "keys": "f2", "command": { "action": "moveTab", "window": "2" }, },
        { "keys": "f3", "command": { "action": "movePane", "window": "1" }, },
        { "keys": "f4", "command": { "action": "movePane", "window": "2" }, },

in their settings, which would allow them to move tabs / panes to other windows using just the keyboard. Is that sufficient?

@zadjii-msft commented on GitHub (Apr 11, 2023): @Saiteja341 The user is free to define actions like: ```jsonc { "keys": "f1", "command": { "action": "moveTab", "window": "1" }, }, { "keys": "f2", "command": { "action": "moveTab", "window": "2" }, }, { "keys": "f3", "command": { "action": "movePane", "window": "1" }, }, { "keys": "f4", "command": { "action": "movePane", "window": "2" }, }, ``` in their settings, which would allow them to move tabs / panes to other windows using just the keyboard. Is that sufficient?
claunia commented 2026-01-31 06:50:51 +00:00
Author
Owner
Copy Link

@Saiteja341 commented on GitHub (Apr 12, 2023):

Hi @zadjii-msft ,

Thanks for providing these command but what if a user doesn't know about these commands, they will not able to perform this functionality.

It should be either pre-define in the terminal's action, So that user might we able to use this functionality with keyboard shortcuts.

@Saiteja341 commented on GitHub (Apr 12, 2023): Hi @zadjii-msft , Thanks for providing these command but what if a user doesn't know about these commands, they will not able to perform this functionality. It should be either pre-define in the terminal's action, So that user might we able to use this functionality with keyboard shortcuts.
claunia commented 2026-01-31 06:50:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2023):

@Saiteja341 Would a default action for "move this tab/pane to a new window" be sufficient here? It should be fairly trivial for us to add a pair of

        { "command": { "action": "moveTab", "window": "new" }, },
        { "command": { "action": "movePane", "window": "new" }, },

default actions, and have them just work out of the box.

@zadjii-msft commented on GitHub (Apr 13, 2023): @Saiteja341 Would a default action for "move this tab/pane to a new window" be sufficient here? It should be fairly trivial for us to add a pair of ``` { "command": { "action": "moveTab", "window": "new" }, }, { "command": { "action": "movePane", "window": "new" }, }, ``` default actions, and have them just work out of the box.
claunia commented 2026-01-31 06:50:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2023):

@Saiteja341 gentle ping ☺️ Would a default action for "move this tab/pane to a new window" be sufficient here?

@zadjii-msft commented on GitHub (Apr 27, 2023): @Saiteja341 gentle ping ☺️ Would a default action for "move this tab/pane to a new window" be sufficient here?
claunia commented 2026-01-31 06:50:52 +00:00
Author
Owner
Copy Link

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

We added the above actions in #15258. If those are insufficient, OP can feel free to reopen.

@zadjii-msft commented on GitHub (May 10, 2023): We added the above actions in #15258. If those are insufficient, OP can feel free to reopen.
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 A11ySev1 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix Product-Terminal WindowsTerminal_Win32
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#19687
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?