microsoft / microsoft/PowerToys

FancyZones Override Windows Snap Adds Extra Unintended Hotkeys to Move Windows

Open
#47,580 2 comments 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Triage Product-FancyZones
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Microsoft PowerToys version

0.99.1

### Installation method

GitHub

### Area(s) with issue?

FancyZones

### Steps to reproduce

So if you have FancyZones `Override Windows Snap` enabled for `Relative Position` .. then `Win+Up/Right/Down/Left` works as expected. The window moves to the relevant FancyZone as expected. But with that setting on, for some reason, `Ctrl+Win+Alt+Left/Right` seem to resize the window as well.

If you turn the setting _OFF_, then those extra keys do not trigger.

### ✔️ Expected Behavior

Is this the intended behaviour? I would expect that "Override Windows Snap" would mean that Windows Snap hot keys would be "disabled" .. or "overridden" in favour of FancyZones. For example, Win+Up would _NOT_ maximise the window if the override is enabled. And certainly, there should not be new extra hotkeys defined out of the blue.

### ❌ Actual Behavior

_No response_

### Upload Bug Report ZIP-file

_No response_

### Additional Information

_No response_

### Other Software

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in FancyZones with Override Windows Snap set to Relative Position, testing the listed Win and Ctrl+Win+Alt shortcuts. Then inspect the FancyZones handling for the override and its hotkey registration; done means the intended Windows shortcuts behave consistently without unintended resize shortcuts.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.