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

Tab switching gets stuck in Settings tab #22993

New Issue
Open
opened 2026-01-31 08:29:24 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:29:24 +00:00
Owner
Copy Link

Originally created by @ferenczy on GitHub (Mar 7, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.22635.4870

Other Software

No response

Steps to reproduce

I have found two bugs that are closely related, as the first one appears during the steps to reproduce the second bug, so I'll put them both together in this issue:

  1. Open a new window with 3 tabs: Settings and two shells
  2. Activate the Settings tab
  3. Press the keyboard shortcut for the action "Next/Previous tab" (usually Ctrl + Tab) so that you keep Ctrl pressed and press Tab just once - the next tab will be activated, but the Tab switcher is not shown (the first bug)
  4. While still keeping Ctrl pressed down, press Tab once again - the last tab will be activated and this time, the Tab switcher finally shows up
  5. While still keeping Ctrl pressed down, press Tab once again - the Settings tab will be activated back
  6. Now finally release the Ctrl key
  7. Press Ctrl + Tab again (this time you can release both keys immediately) - nothing happens, tab switching stopped working altogether, you have to click anywhere on or around settings options to make it work again (the second bug)

Expected Behavior

  1. The Tab switcher should be shown after the first use of "Next/Previous tab" action when you're on the Settings tab, just like it does when any other shell tab is active
  2. When you activate the Settings tab using the "Next/Previous tab" action, it should also be possible to leave the Settings tab the same way without the need to click somewhere first

Actual Behavior

  1. When leaving the Settings tab using the "Next/Previous tab" action, the Tab switcher is shown only after the second use of the action
  2. When the Settings tab is activated using the "Next/Previous tab" action, it's not possible to leave it the same way, unless the user clicks anywhere on or around (in blank space or settings text) the settings options
Originally created by @ferenczy on GitHub (Mar 7, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.22635.4870 ### Other Software _No response_ ### Steps to reproduce I have found two bugs that are closely related, as the first one appears during the steps to reproduce the second bug, so I'll put them both together in this issue: 1. Open a new window with 3 tabs: Settings and two shells 2. Activate the _Settings_ tab 3. Press the keyboard shortcut for the action "Next/Previous tab" (usually `Ctrl` + `Tab`) so that you keep `Ctrl` pressed and press `Tab` just once - the next tab will be activated, but the **_Tab switcher_ is not shown** (the first bug) 4. While still keeping `Ctrl` pressed down, press `Tab` once again - the last tab will be activated and this time, the Tab switcher finally shows up 5. While still keeping `Ctrl` pressed down, press `Tab` once again - the _Settings_ tab will be activated back 6. Now finally release the `Ctrl` key 7. Press `Ctrl` + `Tab` again (this time you can release both keys immediately) - nothing happens, **tab switching stopped working altogether**, you have to click anywhere on or around settings options to make it work again (the second bug) ### Expected Behavior 1. The _Tab switcher_ should be shown after the first use of "Next/Previous tab" action when you're on the _Settings_ tab, just like it does when any other shell tab is active 2. When you activate the _Settings_ tab using the "Next/Previous tab" action, it should also be possible to leave the _Settings_ tab the same way without the need to click somewhere first ### Actual Behavior 1. When leaving the Settings tab using the "Next/Previous tab" action, the Tab switcher is shown only after the second use of the action 2. When the Settings tab is activated using the "Next/Previous tab" action, it's not possible to leave it the same way, unless the user clicks anywhere on or around (in blank space or settings text) the settings options
claunia commented 2026-01-31 08:29:25 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Mar 12, 2025):

Thank you for filing this! It seems that possibly focus is being lost somewhere when we switch into the Settings tab, we'll have to investigate this

@PankajBhojwani commented on GitHub (Mar 12, 2025): Thank you for filing this! It seems that possibly focus is being lost somewhere when we switch into the Settings tab, we'll have to investigate this
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-UserInterface Issue-Bug Needs-Tag-Fix Priority-2 Product-Terminal
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#22993
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?