microsoft / microsoft/PowerToys

[Peek] Incorrect window/content scaling when re-triggering Peek on a different display

Open
#50,193 1 comment 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Triage Product-Peek
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Microsoft PowerToys version and release channel

Current main

### Installation method

Dev build in Visual Studio

### Area(s) with issue?

Peek

### Steps to reproduce

1. On the first display, open an Explorer window and navigate to a directory
2. Select a folder and trigger Peek
3. Drag the Peek window onto the second display which has a different scaling value to the first
4. Select another folder on the first display
5. Trigger Peek again

### ✔️ Expected Behavior

Peek closes on the secondary display and opens again on the first display at the correct size.

### ❌ Actual Behavior

Peek closes on the secondary display and opens again on the first display at the incorrect size:

Image

Correct size:

Image

For images, the image size itself can be incorrect but the window size may be normal, resulting in a large border:

Image

### Upload Bug Report ZIP-file

_No response_

### Additional Information

My displays:

**Primary**
1920 x 1080 at 125% scaling

**Secondary**
3840 x 2160 at 175% scaling

### Other Software

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Peek flow using Explorer across displays with different scaling values, following the listed steps. Trace the Peek entry point for selecting another folder and reopening the window; done means the window and image content reopen on the first display at the correct size without an oversized border.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.