Closed Bug 1762687 Opened 3 years ago Closed 1 year ago

[Wayland] Window size not restored on startup when using fractional scaling

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 98
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: frank.praznik, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

Set the Gnome desktop to 150% scaling on the main, 4k monitor. Open Firefox, resize it to the height of the screen, close and restart.

Actual results:

Upon starting Firefox for the second time, the window is not the same size as when it was closed. Rather, the newly opened window is 75% of the width and height of the screen and needs to be manually restored to the correct size.

The same thing happens when opening a new window from within Firefox, such as when opening a private browser window: rather than match the size of the existing window as it should, the new window is a reduced size.

Expected results:

The window should be the same size when the browser is opened as when it was closed.

Possibly related to bug 1730114 and the window size being clamped to incorrect dimensions?

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Summary: [Wayland] Window size not remembered on startup when using fractional scaling → [Wayland] Window size not restored on startup when using fractional scaling

This is still present in FF 110 and very annoying. I use 125% fractional scaling on a 1080p screen with Fedora (Gnome with Wayland) and new windows are always created at around 2/3 of what they should be.

Blocks: wayland
Priority: -- → P3

This seems to be fixed with fractional scaling enabled in 118. Fractional scaling introduces other already noted issues, but this particular one is resolved.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.