Settings UI doesn't respond to Ctrl+F4 #12499

Closed
opened 2026-01-31 03:17:15 +00:00 by claunia · 4 comments
Owner

Originally created by @bhardwajs on GitHub (Feb 11, 2021).

Environment

Windows build number: 21311.1000
Windows Terminal version (if applicable): 1.6.10272.0

Any other software?

Steps to reproduce

  1. Open Settings UI
  2. Ctrl + F4

Expected behavior

Settings UI should close

Actual behavior

No effect on settings UI.
If I change to another tab, Ctrl + F4 closes that tab.

Originally created by @bhardwajs on GitHub (Feb 11, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 21311.1000 Windows Terminal version (if applicable): 1.6.10272.0 Any other software? ``` # Steps to reproduce 1. Open Settings UI 2. Ctrl + F4 <!-- A description of how to trigger this bug. --> # Expected behavior Settings UI should close <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior No effect on settings UI. If I change to another tab, Ctrl + F4 closes that tab. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 03:17:15 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Feb 11, 2021):

Do you have Ctrl+F4 bound in your settings? I'm trying to figure out if the "close tab" behavior you're getting is the one built-in to the tab control, or the one that the Terminal implements.

I'm thinking that this is a blend between #8585 and #8767

@zadjii-msft commented on GitHub (Feb 11, 2021): Do you have <kbd>Ctrl+F4</kbd> bound in your settings? I'm trying to figure out if the "close tab" behavior you're getting is the one built-in to the tab control, or the one that the Terminal implements. I'm thinking that this is a blend between #8585 and #8767
Author
Owner

@bhardwajs commented on GitHub (Feb 11, 2021):

@zadjii-msft I don't have Ctrl+F4 bound in my settings. Testing right now, behavior is close to #8585 in that Ctrl+F4 has no effect until I am on the title bar.

@bhardwajs commented on GitHub (Feb 11, 2021): @zadjii-msft I don't have `Ctrl+F4` bound in my settings. Testing right now, behavior is close to #8585 in that `Ctrl+F4` has no effect until I am on the title bar.
Author
Owner

@zadjii-msft commented on GitHub (Feb 12, 2021):

Alright, then I'm gonna close this one as a duplicate. Thanks!

/dup #8585

@zadjii-msft commented on GitHub (Feb 12, 2021): Alright, then I'm gonna close this one as a duplicate. Thanks! /dup #8585
Author
Owner

@ghost commented on GitHub (Feb 12, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 12, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12499