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

A hidden mouse cursor won't reappear when moved if over a tab #12236

New Issue
Closed
opened 2026-01-31 03:09:55 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:09:55 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Jan 28, 2021).

Environment

Windows build number: Version 10.0.18363.1256
Windows Terminal version (if applicable): commit d29d72e1e0

Steps to reproduce

  1. You'll need to be running a build of WT that includes the mouse hiding feature introduced in PR #8629.
  2. Move the mouse so it's positioned over one of the tab labels.
  3. Start typing something so the mouse cursor disappears.
  4. Try and move the mouse, but without moving off the label.

Expected behavior

The mouse cursor should reappear.

Actual behavior

The mouse cursor remains invisible until you move it onto the main output area of the window. But you can still see focus interactions, and tooltips changing, as you move over the tab controls.

Interestingly, if you move the mouse right off the WT window, it will become visible, but then moving back onto a tab will make it disappear again.

Originally created by @j4james on GitHub (Jan 28, 2021). # Environment Windows build number: Version 10.0.18363.1256 Windows Terminal version (if applicable): commit d29d72e1e023491800b6a03bc226c35e5f9ec240 # Steps to reproduce 1. You'll need to be running a build of WT that includes the mouse hiding feature introduced in PR #8629. 2. Move the mouse so it's positioned over one of the tab labels. 3. Start typing something so the mouse cursor disappears. 4. Try and move the mouse, but without moving off the label. # Expected behavior The mouse cursor should reappear. # Actual behavior The mouse cursor remains invisible until you move it onto the main output area of the window. But you can still see focus interactions, and tooltips changing, as you move over the tab controls. Interestingly, if you move the mouse right off the WT window, it will become visible, but then moving back onto a tab will make it disappear again.
claunia commented 2026-01-31 03:09:56 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 28, 2021):

😢 - I guess the TabView is capturing the pointer move events somehow.

@Don-Vito commented on GitHub (Jan 28, 2021): 😢 - I guess the TabView is capturing the pointer move events somehow.
claunia commented 2026-01-31 03:09:57 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 28, 2021):

I tried the following

  1. Added PointerMoveHandler to TerminalPage - it didn't help, the event is not getting fired (probably the TabView captures the pointer)
  2. Added PointerEntered and PointerExited to the TerminalControl, and changed the logic so the Hide will be fired only if the mouse within the bounds of the termcontrol. The problem is that sometimes PointerEntered is not triggered (e.g., when you close a fly-out)
  3. Added a VisualTreeHelper upon hide, to check if TermControl captures pointer position. Seems extremely inefficient.
@Don-Vito commented on GitHub (Jan 28, 2021): I tried the following 1. Added PointerMoveHandler to TerminalPage - it didn't help, the event is not getting fired (probably the TabView captures the pointer) 2. Added PointerEntered and PointerExited to the TerminalControl, and changed the logic so the Hide will be fired only if the mouse within the bounds of the termcontrol. The problem is that sometimes PointerEntered is not triggered (e.g., when you close a fly-out) 3. Added a VisualTreeHelper upon hide, to check if TermControl captures pointer position. Seems extremely inefficient.
claunia commented 2026-01-31 03:09:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

Oof, yeah. I had similar trouble with the implementation of the I-beam cursor over the control. It drives me mad that the cursor is a property of the application window, but controls need to individually set it. Absolutely mad.

@DHowett commented on GitHub (Jan 28, 2021): Oof, yeah. I had similar trouble with the implementation of the I-beam cursor over the control. It drives me *mad* that the cursor is a property of the application window, but controls need to individually set it. Absolutely mad.
claunia commented 2026-01-31 03:09:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

/cc @zadjii-msft triage decision: 1.7

@DHowett commented on GitHub (Jan 28, 2021): /cc @zadjii-msft triage decision: 1.7
claunia commented 2026-01-31 03:09:57 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 28, 2021):

@DHowett - is it still possible to fix / rollback it for 1.6 Preview?

@Don-Vito commented on GitHub (Jan 28, 2021): @DHowett - is it still possible to fix / rollback it for 1.6 Preview?
claunia commented 2026-01-31 03:09:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

NOPE, but I can include a rollback or a fix in a servicing update.

@DHowett commented on GitHub (Jan 28, 2021): NOPE, but I can include a rollback or a fix in a servicing update.
claunia commented 2026-01-31 03:09:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 28, 2021):

That's W I L D. I don't think it's that bad that we need to release a 1.6 hotfix to roll this back, but we should definitely have a fix for 1.6 stable.

@zadjii-msft commented on GitHub (Jan 28, 2021): That's W I L D. I don't think it's _that_ bad that we need to release a 1.6 hotfix to roll this back, but we should definitely have a fix for 1.6 _stable_.
claunia commented 2026-01-31 03:09:58 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 28, 2021):

Yeah, the only reason I noticed this was because I was doing some testing where I needed to repeatedly open and close a tab, and I had the mouse hovering over the tab so I could quickly get to the close button. That's not exactly typical usage, so I think it's unlikely many people will encounter this issue.

@j4james commented on GitHub (Jan 28, 2021): Yeah, the only reason I noticed this was because I was doing some testing where I needed to repeatedly open and close a tab, and I had the mouse hovering over the tab so I could quickly get to the close button. That's not exactly typical usage, so I think it's unlikely many people will encounter this issue.
claunia commented 2026-01-31 03:09:58 +00:00
Author
Owner
Copy Link

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

:tada:This issue was addressed in #8952, which has now been successfully released as Windows Terminal Preview v1.6.10412.0.🎉

Handy links:

@ghost commented on GitHub (Feb 11, 2021): :tada:This issue was addressed in #8952, which has now been successfully released as `Windows Terminal Preview v1.6.10412.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.6.10412.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-TerminalControl Help Wanted Issue-Bug Needs-Tag-Fix Priority-2 Product-Terminal Resolution-Fix-Committed
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#12236
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?