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

Feature request: Input focus follows mouse #7299

New Issue
Open
opened 2026-01-31 01:00:29 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:00:29 +00:00
Owner
Copy Link

Originally created by @LookoutHill on GitHub (Apr 6, 2020).

Description of the new feature/enhancement

Focus follows mouse allows one to direct input into the exposed terminal tab while another window is selected so long as the mouse pointer is positioned anywhere over the Windows Terminal window.

This will reduce extra mouse clicks and make switching input focus more streamlined.

Proposed technical implementation details (optional)

Given that another window is selected and active, focus follows mouse allows one to direct input into the exposed terminal tab when the mouse pointer is positioned anywhere over the Windows Terminal window. One does not have to click on the Windows Terminal window to active input focus.

Originally created by @LookoutHill on GitHub (Apr 6, 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! --> # Description of the new feature/enhancement Focus follows mouse allows one to direct input into the exposed terminal tab while another window is selected so long as the mouse pointer is positioned anywhere over the Windows Terminal window. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> This will reduce extra mouse clicks and make switching input focus more streamlined. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Given that another window is selected and active, focus follows mouse allows one to direct input into the exposed terminal tab when the mouse pointer is positioned anywhere over the Windows Terminal window. One does not have to click on the Windows Terminal window to active input focus.
claunia added the Help WantedIssue-TaskProduct-TerminalArea-UserInterface labels 2026-01-31 01:00:29 +00:00
claunia commented 2026-01-31 01:00:30 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 8, 2020):

Yeah, this is a neat feature request. I'm marking it up for terminal/UI/backlog and that it needs a specification 😄

@DHowett-MSFT commented on GitHub (Apr 8, 2020): Yeah, this is a neat feature request. I'm marking it up for terminal/UI/backlog and that it needs a specification :smile:
claunia commented 2026-01-31 01:00:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 22, 2021):

Huh, so this is different from #6459 (which was added in Windows Terminal Preview v1.7.572.0). For this, we just need to focus the window when the get a mouse hover event, even when the Terminal isn't focused. I suppose a "window"/global setting for "focusOnHover":bool would be easy enough (so long as we get the right window message even when inactive. Don't think we need a whole spec for this one.

@zadjii-msft commented on GitHub (Nov 22, 2021): Huh, so this is different from #6459 (which was added in `Windows Terminal Preview v1.7.572.0`). For this, we just need to focus the window when the get a mouse hover event, even when the Terminal isn't focused. I suppose a "window"/global setting for `"focusOnHover":bool` would be easy enough (so long as we get the right window message even when inactive. Don't think we need a whole spec for this one.
claunia commented 2026-01-31 01:00:31 +00:00
Author
Owner
Copy Link

@alceu-frigeri commented on GitHub (Aug 21, 2022):

If I may, 'focus follows the mouse' is kind of already implemented (although oddly named) : control panel -> ease of access -> ease of access center -> make the mouse easier to use -> activate a window by hovering over it ...

which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow.

It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows).

Even better if one had the added option to tell windows "bring the window to the top ONLY IF the user click the top bar, but not otherwise"

@alceu-frigeri commented on GitHub (Aug 21, 2022): If I may, 'focus follows the mouse' is kind of already implemented (although oddly named) : control panel -> ease of access -> ease of access center -> make the mouse easier to use -> activate a window by hovering over it ... which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow. It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows). Even better if one had the added option to tell windows "bring the window to the top ONLY IF the user click the top bar, but not otherwise"
claunia commented 2026-01-31 01:00:31 +00:00
Author
Owner
Copy Link

@b- commented on GitHub (Sep 14, 2022):

[...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow.

It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows).

@alceu-frigeri try this

I use it all the time.

@b- commented on GitHub (Sep 14, 2022): > [...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow. > > It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows). @alceu-frigeri try [this](https://winaero.com/turn-on-xmouse-active-window-tracking-focus-follows-mouse-pointer-feature-in-windows-8-1-windows-8-and-windows-7/?utm_source=software&utm_medium=in-app&utm_campaign=winaerotweaker&utm_content=xmouse) I use it all the time.
claunia commented 2026-01-31 01:00:31 +00:00
Author
Owner
Copy Link

@alceu-frigeri commented on GitHub (Sep 14, 2022):

[...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow.
It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows).

@alceu-frigeri try this

I use it all the time.

Thanks,
I kind of knew that, through registry you can force that behavior,
the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'.

@alceu-frigeri commented on GitHub (Sep 14, 2022): > > [...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow. > > It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows). > > @alceu-frigeri try [this](https://winaero.com/turn-on-xmouse-active-window-tracking-focus-follows-mouse-pointer-feature-in-windows-8-1-windows-8-and-windows-7/?utm_source=software&utm_medium=in-app&utm_campaign=winaerotweaker&utm_content=xmouse) > > I use it all the time. Thanks, I kind of knew that, through registry you can force that behavior, the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'.
claunia commented 2026-01-31 01:00:31 +00:00
Author
Owner
Copy Link

@b- commented on GitHub (Sep 15, 2022):

[...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow.
It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows).

@alceu-frigeri try this
I use it all the time.

Thanks, I kind of knew that, through registry you can force that behavior, the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'.

I understand, but I don't think the teams responsible for Windows's own settings are anywhere near this GitHub issue page. I recommend filing a report in Feedback Hub (and if you link it here I'll vote on it!). But I personally just install that silly WinAero Tweaker app and use that, or it would be relatively trivial to write a small C++ application that computes and applies the correct settings. You absolutely don't need administrator access to change those registry settings. (Former sysadmin)

@b- commented on GitHub (Sep 15, 2022): > > > [...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow. > > > It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows). > > > > > > @alceu-frigeri try [this](https://winaero.com/turn-on-xmouse-active-window-tracking-focus-follows-mouse-pointer-feature-in-windows-8-1-windows-8-and-windows-7/?utm_source=software&utm_medium=in-app&utm_campaign=winaerotweaker&utm_content=xmouse) > > I use it all the time. > > Thanks, I kind of knew that, through registry you can force that behavior, the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'. I understand, but I don't think the teams responsible for Windows's own settings are anywhere near this GitHub issue page. I recommend filing a report in Feedback Hub (and if you link it here I'll vote on it!). But I personally just install that silly WinAero Tweaker app and use that, or it would be _relatively_ trivial to write a small C++ application that computes and applies the correct settings. You absolutely don't need administrator access to change those registry settings. (Former sysadmin)
claunia commented 2026-01-31 01:00:32 +00:00
Author
Owner
Copy Link

@alceu-frigeri commented on GitHub (Sep 15, 2022):

[...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow.
It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows).

@alceu-frigeri try this
I use it all the time.

Thanks, I kind of knew that, through registry you can force that behavior, the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'.

I understand, but I don't think the teams responsible for Windows's own settings are anywhere near this GitHub issue page. I recommend filing a report in Feedback Hub (and if you link it here I'll vote on it!). But I personally just install that silly WinAero Tweaker app and use that, or it would be relatively trivial to write a small C++ application that computes and applies the correct settings. You absolutely don't need administrator access to change those registry settings. (Former sysadmin)

to make it short: yes, I know that there are ways 'to force that behavior', and yes too, I already 'posted a request in the feedback hub' (and same 'nonresponse response' as here.
If you have the knowledge to edit the registry, go for it. do it, be happy. I'm too old to have to keep a tab of what registry do I have to set to which hidden feature in said version. nonsense (like trying to convince someone that never used a project-based system manager that using one is nice: 'too complicated')

@alceu-frigeri commented on GitHub (Sep 15, 2022): > > > > [...] which 'sucks' because, once you activate this option, wherever you move the mouse, the hovering window comes to top, completely disrupting (at least for me) my workflow. > > > > It would be really nice if the focus would follow the mouse BUT without bringing the focused window to the top (allowing one to type/input in a partially covered window). btw, this is the behavior one can have in Linux KDE (Xwindows). > > > > > > > > > @alceu-frigeri try [this](https://winaero.com/turn-on-xmouse-active-window-tracking-focus-follows-mouse-pointer-feature-in-windows-8-1-windows-8-and-windows-7/?utm_source=software&utm_medium=in-app&utm_campaign=winaerotweaker&utm_content=xmouse) > > > I use it all the time. > > > > > > Thanks, I kind of knew that, through registry you can force that behavior, the problem with solutions of the kind 'you have to remember to adjust it in the registry', and some times it isn't an option (corporate PCs), that's why I tried to ask: 'make it an UI option'. > > I understand, but I don't think the teams responsible for Windows's own settings are anywhere near this GitHub issue page. I recommend filing a report in Feedback Hub (and if you link it here I'll vote on it!). But I personally just install that silly WinAero Tweaker app and use that, or it would be _relatively_ trivial to write a small C++ application that computes and applies the correct settings. You absolutely don't need administrator access to change those registry settings. (Former sysadmin) to make it short: yes, I know that there are ways 'to force that behavior', and yes too, I already 'posted a request in the feedback hub' (and same 'nonresponse response' as here. If you have the knowledge to edit the registry, go for it. do it, be happy. I'm too old to have to keep a tab of what registry do I have to set to which hidden feature in said version. nonsense (like trying to convince someone that never used a project-based system manager that using one is nice: 'too complicated')
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 Help Wanted Issue-Task 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#7299
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?