Focus is not moved to cursor when switching from another application #9828

Closed
opened 2026-01-31 02:04:57 +00:00 by claunia · 3 comments
Owner

Originally created by @NeilMacMullen on GitHub (Jul 24, 2020).

Environment

Windows build number: Version	10.0.19041 Build 19041

Windows Terminal version:1.2.2022.0

Steps to reproduce

  • Ensure "snapOnInput": true, is set in default profile settings.

  • Start a new terminal session/window.

  • Ensure that there are two shell tabs open in the window. (I use 2 powershell tabs but it doesn't seem important exactly which are used).

  • Open Notepad or some other application of your choice.

  • Change the focus to notepad and type into the window.

  • Click on the first tab header in Terminal (important - must be header, not editing pane)

  • Start typing - note that no text appears at the cursor in the Terminal pane pane.

  • The expected behavior would be that text would appear the cursor

  • Note that if you then click on the header of the second tab and start typing, text is displayed at cursor so this appears to be an issue to do with the initial application focus.

Expected behavior

As above, changing focus to terminal from another application by clicking on a tab header should move text-entry focus to the editing pane.

Actual behavior

See above.

Originally created by @NeilMacMullen on GitHub (Jul 24, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ``` Windows build number: Version 10.0.19041 Build 19041 Windows Terminal version:1.2.2022.0 ``` # Steps to reproduce - Ensure "snapOnInput": true, is set in default profile settings. - Start a new terminal session/window. - Ensure that there are two shell tabs open in the window. (I use 2 powershell tabs but it doesn't seem important exactly which are used). - Open Notepad or some other application of your choice. - Change the focus to notepad and type into the window. - Click on the first tab header in Terminal (important - must be header, not editing pane) - Start typing - note that no text appears at the cursor in the Terminal pane pane. - The **expected behavior** would be that text would appear the cursor - _Note that if you then click on the header of the second tab and start typing, text _is_ displayed at cursor so this appears to be an issue to do with the initial application focus._ # Expected behavior As above, changing focus to terminal from another application by clicking on a tab header should move text-entry focus to the editing pane. # Actual behavior See above.
claunia added the Resolution-Duplicate label 2026-01-31 02:04:57 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jul 24, 2020):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3609 and #6680 for more discussion.

/dup #3609

@zadjii-msft commented on GitHub (Jul 24, 2020): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3609 and #6680 for more discussion. /dup #3609
Author
Owner

@ghost commented on GitHub (Jul 24, 2020):

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 (Jul 24, 2020): 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!
Author
Owner

@NeilMacMullen commented on GitHub (Jul 24, 2020):

Thanks @zadjii-msft ! I did have a look through the backlog of "focus" issues but missed that one. Keep up the great work - I'm liking the new terminal a lot.

@NeilMacMullen commented on GitHub (Jul 24, 2020): Thanks @zadjii-msft ! I did have a look through the backlog of "focus" issues but missed that one. Keep up the great work - I'm liking the new terminal a lot.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9828