1783414 - [Wayland] Firefox window becomes tiny if you maximize Firefox, disable the titlebar under Customize and then unmaximize Firefox.

Status: NEW

(Core :: Widget: Gtk, defect)

Description

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Attachment: ubuntu screen size.webm

Found in

• Firefox 105.0a1

Affected versions

• Firefox 104.0b6
• Firefox 105.0a1

Affected platforms

• Ubuntu 22.04

Steps to reproduce

1. Launch Firefox and stretch the window to the screen
2. Enter customize mode and activate Title bar
3. Double click on the top bar of the browser in order to shrink the window

Expected result

• The window shrinks to the previous saved window dimension (default)

Actual result

• The window is shrinked to the minimum possible size

Regression range

• Will see for a regression

Additional notes

• The issue can be seen in the attachment
• macOS and Windows are not affected

Comment 1

[Daniel Bodea [:danibodea]]

This will not help much, but at least we can be sure that it reproduces since wayland was activated.

Last good revision: 5ed2c0d1e7819e74a8816219e6154f1707e52d85
First bad revision: 96732a2f2846c158ac1c1dc9f1f2f9b1d676df83
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5ed2c0d1e7819e74a8816219e6154f1707e52d85&tochange=96732a2f2846c158ac1c1dc9f1f2f9b1d676df83

Comment 2

[lilydjwg]

I have seen very small Firefox windows on Arch Linux with wayfire too, but not sure how it was triggered (not Customize).

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1749174

:emilio, since you are the author of the regressor, bug 1749174, could you take a look?
For more information, please visit auto_nag documentation.

Comment 4

[Emilio Cobos Álvarez [:emilio]]

Would it be possible to try to find a regression range with MOZ_ENABLE_WAYLAND=1 in the environment?

Though I think this might not be quite in our control...

Comment 5

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Hey Emilio, sorry for the late response. I just tried with MOZ_ENZBLE_WAYLAND=1 but nothing changes. It seems to have something with the Ubuntu wayland session though, as I wasn't able to reproduce this on x11 session, but reproduces easily on "Ubuntu on wayland" from the user selection.

Comment 6

[Darkspirit]

Tested on KDE Wayland, Debian Testing, Intel:
Still reproducible. This exists since wayland support was added in bug 1501218.
Does not occur on Xwayland.

MOZ_DISABLE_CONTENT_SANDBOX=1 MOZ_ENABLE_WAYLAND=1 mozregression --good 2019-01-01 --bad 2020-01-01

4:53.66 INFO: Last good revision: d305772af471766618393c01065556e739738e84 (2019-01-28)
4:53.66 INFO: First bad revision: 4440fbf71c72e13cfcb6257bbae6024052ffd46d (2019-01-29)
4:53.66 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d305772af471766618393c01065556e739738e84&tochange=4440fbf71c72e13cfcb6257bbae6024052ffd46d

likely

b9424178ab0b44acb8fa9a39b686b1e3d8cec9a8 Martin Stransky — Bug 1522780 - [Wayland] Use MOZ_ENABLE_WAYLAND to enable wayland backend, r=glandium

---

"good" = 2018-01-01 + 2018-07-03 + 2018-10-02 + 2018-10-25 + 2018-11-06 + 2018-11-12 + 2018-11-14 = startup crash
bad = 2019-01-01 = reproducible
MOZ_DISABLE_CONTENT_SANDBOX=1 GDK_BACKEND=wayland mozregression --good 2018-01-01 --bad 2019-01-01

4:30.46 INFO: Last good revision: b0a40093b6b7a0784a6f38b318f597419d86fd8e (2018-11-14)
4:30.46 INFO: First bad revision: 0051c8d339a969d80b66e6ce243091a9dbb6a319 (2018-11-15)
4:30.46 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b0a40093b6b7a0784a6f38b318f597419d86fd8e&tochange=0051c8d339a969d80b66e6ce243091a9dbb6a319

likely

6fc6bdea42a60b7e3fb426beb073e07a3922913c Mike Hommey — Bug 1501218 - Enable wayland support with --enable-default-toolkit=cairo-gtk3. r=mshal