Description
[v3] On macOS, the Screen Bounds and WorkArea halved on Retina displays.
On macOS, application.Screen returns Bounds, WorkArea, and Size values that are half the real display
dimensions on any Retina display (backingScaleFactor > 1). PhysicalBounds and PhysicalWorkArea report the
actual point values of the display, not device pixels as their names suggest.
- Windows sized as a fraction of the work area end up roughly half the expected size, often clamping to
configured minimums.
- Centering logic places windows based on half-sized screen rects, so windows appear offset or in the wrong
quadrant.
- Any app that queries app.Screen.GetPrimary() / .GetAll() to lay out, snap, or position windows is
affected.
- screen_windows.go and screen_linux.go are unaffected — this is macOS-only.
To Reproduce
...
Expected behaviour
...
Screenshots
...
Attempted Fixes
...
System Details
Additional context
No response
Description
[v3] On macOS, the Screen Bounds and WorkArea halved on Retina displays.
On macOS, application.Screen returns Bounds, WorkArea, and Size values that are half the real display
dimensions on any Retina display (backingScaleFactor > 1). PhysicalBounds and PhysicalWorkArea report the
actual point values of the display, not device pixels as their names suggest.
configured minimums.
quadrant.
affected.
To Reproduce
...
Expected behaviour
...
Screenshots
...
Attempted Fixes
...
System Details
Additional context
No response