rapidly clicking causing flickering of window focus

[BPplays]

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:

[carlos-zamora]

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/?

[BPplays]

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

[carlos-zamora]

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

[zadjii-msft]

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.