Description
In a Windows 11 multi-monitor environment with a Mixed-DPI setup, Min browser progressively shrinks its window size every time it is closed and reopened when placed on the secondary monitor.
It seems that during the shutdown process, Min incorrectly recalculates the current window dimensions based on the primary monitor's DPI scale factor instead of the active monitor's, causing the dimensions to be divided by 1.5x before saving them to windowBounds.json.
Steps to Reproduce
- Set up a multi-monitor environment:
- Primary Monitor: 4K resolution with 150% DPI Scaling
- Secondary Monitor: 1080p resolution with 100% DPI Scaling
- Launch Min and move the window to the secondary (1080p) monitor.
- Resize the window to a preferred size (non-maximized) and close it.
- Check
windowBounds.json or relaunch Min.
- Repeat closing and opening the browser without manually resizing it.
Expected Behavior
The browser should preserve the exact window size (width and height) across restarts, regardless of which monitor it is placed on.
Actual Behavior
-
On the Secondary Monitor (1080p, 100%): The window size shrinks consecutively on every close. For example, the values saved in windowBounds.json change like this sequentially:
- First close:
{"x":2328,"y":428,"width":1170,"height":630,"maximized":false}
- Second close:
{"x":2328,"y":428,"width":784,"height":424,"maximized":false}
- Third close:
{"x":2328,"y":428,"width":529,"height":353,"maximized":false}
- Fourth close:
{"x":2328,"y":428,"width":404,"height":353,"maximized":false}
(Note: 1170 / 1.5 ≈ 780, 784 / 1.5 ≈ 522... It clearly shows the dimensions are being divided by the primary monitor's 1.5x scale factor on every save event, even though the window resides on the 100% scaling monitor.)
-
On the Primary Monitor (4K, 150%): The window size is correctly preserved across restarts. The shrinking bug does NOT occur at all when Min is kept and closed on the primary monitor.
-
Maximized Window: If the window is closed while maximized on either monitor, "maximized": true is properly maintained, and this shrinking issue does not occur.
Environment
- Min Version: 1.35.5
- OS Specifications:
- Edition: Windows 11 Pro
- Version: 25H2
- OS Build: 26200.8457
- Display Setup: - Multi-monitor (Mixed-DPI)
- Main: 4K (150% DPI)
- Sub: 1080p (100% DPI) — The bug specifically occurs when running on this monitor
Description
In a Windows 11 multi-monitor environment with a Mixed-DPI setup, Min browser progressively shrinks its window size every time it is closed and reopened when placed on the secondary monitor.
It seems that during the shutdown process, Min incorrectly recalculates the current window dimensions based on the primary monitor's DPI scale factor instead of the active monitor's, causing the dimensions to be divided by 1.5x before saving them to
windowBounds.json.Steps to Reproduce
windowBounds.jsonor relaunch Min.Expected Behavior
The browser should preserve the exact window size (width and height) across restarts, regardless of which monitor it is placed on.
Actual Behavior
On the Secondary Monitor (1080p, 100%): The window size shrinks consecutively on every close. For example, the values saved in
windowBounds.jsonchange like this sequentially:{"x":2328,"y":428,"width":1170,"height":630,"maximized":false}{"x":2328,"y":428,"width":784,"height":424,"maximized":false}{"x":2328,"y":428,"width":529,"height":353,"maximized":false}{"x":2328,"y":428,"width":404,"height":353,"maximized":false}(Note: 1170 / 1.5 ≈ 780, 784 / 1.5 ≈ 522... It clearly shows the dimensions are being divided by the primary monitor's 1.5x scale factor on every save event, even though the window resides on the 100% scaling monitor.)
On the Primary Monitor (4K, 150%): The window size is correctly preserved across restarts. The shrinking bug does NOT occur at all when Min is kept and closed on the primary monitor.
Maximized Window: If the window is closed while maximized on either monitor,
"maximized": trueis properly maintained, and this shrinking issue does not occur.Environment