starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

rapidly clicking causing flickering of window focus #21277

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

Originally created by @BPplays on GitHub (Feb 19, 2024).

Windows Terminal version

1.20.10303.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

rapidly clicking seems to cause flickering of window focus.
it seems to need precise timing to trigger, i've accidentally triggered it with a double click before

Expected Behavior

No response

Actual Behavior

click to watch:
click to watch

Originally created by @BPplays on GitHub (Feb 19, 2024). ### Windows Terminal version 1.20.10303.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce rapidly clicking seems to cause flickering of window focus. it seems to need precise timing to trigger, i've accidentally triggered it with a double click before ### Expected Behavior _No response_ ### Actual Behavior click to watch: [![click to watch](https://cdn.discordapp.com/attachments/351325525886763008/1209275047630340116/5COYYJiZHHg-HD.jpg?ex=65e65426&is=65d3df26&hm=e39528c3b13b4d7464b81beced988d22bf40b79f802dc349bde154f042a325ce&)](https://www.youtube.com/watch?v=5COYYJiZHHg)
claunia added the Issue-BugProduct-TerminalArea-Windowing labels 2026-01-31 07:38:29 +00:00
claunia commented 2026-01-31 07:38:30 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 21, 2024):

Thanks for filing! Does this happen regardless of what you're running inside terminal? Or when there's a specific number of tabs? Any 3rd party window management software? Can you also share your settings.json file/?

@carlos-zamora commented on GitHub (Feb 21, 2024): Thanks for filing! Does this happen regardless of what you're running inside terminal? Or when there's a specific number of tabs? Any 3rd party window management software? Can you also share your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file)/?
claunia commented 2026-01-31 07:38:30 +00:00
Author
Owner
Copy Link

@BPplays commented on GitHub (Feb 21, 2024):

this seems to only happen if you have a lot of tabs open i tested with 38 tabs just now and it worked but it might work with less.

im using DisplayFusion Pro 10.0 and PowerToys v0.76.2 FancyZones

settings.json

@BPplays commented on GitHub (Feb 21, 2024): this seems to only happen if you have a lot of tabs open i tested with 38 tabs just now and it worked but it might work with less. im using DisplayFusion Pro 10.0 and PowerToys v0.76.2 FancyZones [settings.json](https://github.com/microsoft/terminal/files/14366062/settings_upload.json)
claunia commented 2026-01-31 07:38:31 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 28, 2024):

Thanks! We've managed to reproduce it. Btw, your settings file is a work of art. Thanks :)

@carlos-zamora commented on GitHub (Feb 28, 2024): Thanks! We've managed to reproduce it. Btw, your settings file is a work of art. Thanks :)
claunia commented 2026-01-31 07:38:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 28, 2024):

I'm guessing that this is pretty close to the same thing as #13771. From that thread:

This is fallout from the fix to #13589, more or less.

For whatever reason, the taskbar is restoring the hidden tool window ("pseudowindow") that's attached to the Terminal, rather than the actual Terminal window. Before we fixed #13589, the Terminal just wouldn't restore from the taskbar at all. Instead, we now can determine that the tool window got restored, and we send a signal to the Terminal to cause it to get restored as well. HOWEVER, we need to debounce these requests for various reasons. So there's a 200ms throttling that happens, which delays the restore (but also prevents CRAZY FLASHING) of the terminal window.

This is all fixed in Windows 11 (there, the taskbar just restores the Terminal's main HWND).

There's also #13388 and #13640 which are tracking additional weird bugs about this scenario. Considering we need to still figure out these last Windows 10 issues, I'm considering rolling them all into one thread.

I'm thinking in your case, because there's SO many tabs that are open, the delay between the first window changing state and the last one, is long enough that they get stuck in a loop.

Leonard just now was able to locally confirm this and noted that specifically the threshold for his machine was 32 tabs. Fewer than that - no repro. So wt -w 0 nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt first to get into that state.

@zadjii-msft commented on GitHub (Feb 28, 2024): I'm guessing that this is pretty close to the same thing as #13771. From that thread: > This is fallout from the fix to #13589, more or less. > > For whatever reason, the taskbar is restoring the hidden tool window ("pseudowindow") that's attached to the Terminal, rather than the actual Terminal window. Before we fixed #13589, the Terminal just wouldn't restore from the taskbar _at all_. Instead, we now can determine that the tool window got restored, and we send a signal to the Terminal to cause it to get restored as well. HOWEVER, we need to debounce these requests for various reasons. So there's a 200ms throttling that happens, which delays the restore (but also prevents CRAZY FLASHING) of the terminal window. > > This is all fixed in Windows 11 (there, the taskbar just restores the Terminal's main HWND). > > There's also #13388 and #13640 which are tracking additional weird bugs about this scenario. Considering we need to still figure out these last Windows 10 issues, I'm considering rolling them all into one thread. I'm thinking in your case, because there's SO many tabs that are open, the delay between the first window changing state and the last one, is long enough that they get stuck in a loop. Leonard just now was able to locally confirm this and noted that specifically the threshold for his machine was 32 tabs. Fewer than that - no repro. So `wt -w 0 nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt;nt` first to get into that state.
claunia commented 2026-01-31 07:38:31 +00:00
Author
Owner
Copy Link

@hwf1324 commented on GitHub (Dec 2, 2025):

I'm not sure if I'm encountering the same issue?

In my case, it's mostly with git bash configurations. Sometimes when selecting content, and sometimes just by clicking, the content of that tab will flicker white extensively. At this point, no operations can be performed. However, it might recover after being left alone for a while.

This doesn't require a large number of tabs.

@hwf1324 commented on GitHub (Dec 2, 2025): I'm not sure if I'm encountering the same issue? In my case, it's mostly with git bash configurations. Sometimes when selecting content, and sometimes just by clicking, the content of that tab will flicker white extensively. At this point, no operations can be performed. However, it might recover after being left alone for a while. This doesn't require a large number of tabs.
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-Windowing Issue-Bug 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#21277
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?