Powertoys: Google Chrome Tab becoming White when Merging

[Drakardus]

ℹ Computer information

• PowerToys version: Version v0.20.1
• PowerToy Utility: FancyZones
• Running PowerToys as Admin: Yes
• Windows build number: [run "winver"] 1803

📝 Provide detailed reproduction steps (if any)

1. Using Google Chrome, when moving a tab to merge with the browser. FancyZone interferes and makes the tab that the user wants to merge with the browser becomes white and takes around a minute to close manually.

✔️ Expected result

To merge a google chrome tab to the browser

❌ Actual result

instead of merging the tab becomes white with invisible Minimize, Enlarge, Close. Takes a minute to close manually

📷 Screenshots

_Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form_

[enricogior]

@Drakardus
please provide more details repro steps.
Do you have the "Hold Shift key to activate..." option on or off?
Do you have the "Make dragged window transparent" option on or off?
Does this happens all the time?
If you quit PowerToys, does the problem go away?

[rcmaehl]

ℹ Computer information

PowerToys version: Version v0.20.1
PowerToy Utility: FancyZones
Running PowerToys as Admin: Yes
Windows build number: [run "winver"] 2004

Hi @enricogior, @crutkas and others,

I'm also having this issue. Here's my powertoys settings:

I can occasionally reproduce this by

1. Create multiple zones
2. Open several Chrome tabs
3. Attempt to detach a tab from Chrome into it's own Window
4. Chrome triggers Fancy Zones snap and stops drawing/update as seen below

The specific detached chrome tab (and now Window) stops drawing/compositing and is generally unusable at this point excluding the context menu

Forcibly moving the Window to a new zone also compounds the issue:

The only way to close the now bricked chrome tab is to use Chrome's task manager from other Window.

I'm 100% certain this isn't a bug with PowerToys but an extreme edge case in chrome causing some sort of race condition. A simple delay of a couple seconds before activating fancyzones for a new chrome window should be a reasonable work around.

[pokemav]

this is same issue #3536 reported back in May and still not fixed...

don't bother.. it's been ignored since then

[rcmaehl]

I wouldn't say #3859 is a duplicate but #3536 definitely is

[pokemav]

I wouldn't say #3859 is a duplicate but #3536 definitely is

true, my mistake, corrected already. Thanks

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[enricogior]

We made some fixing in 0.23 that may effect this issue as well.

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[rcmaehl]

We made some fixing in 0.23 that may effect this issue as well.

Is 0.23 the master branch as found here; https://dev.azure.com/ms/PowerToys/_build ?

Or would I have to compile myself from a branch

[crutkas]

Is 0.23 the master branch as found here; https://dev.azure.com/ms/PowerToys/_build ?
Or would I have to compile myself from a branch

You have to compile it yourself. We haven't quiet gotten to nightly builds yet.

[pokemav]

.23 release build and problem is still present. Hopefully will be fixed by the end of the year. It's been months since this regression.

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[rcmaehl]

Can confirm, issue still persists

[enricogior]

A fix will be available in 0.23.2