1852931 - Resizing the window doesn't resize the content (page, navbar & tabs)

Status: RESOLVED INCOMPLETE

(Firefox :: Tabbed Browser, defect)

Description

[legmatt0]

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

Steps to reproduce:

The problem happens after an amount of time browsing.
I've seen the problem several times across two computers (Both with gnome wayland). I initially thought it was a Wayland bug, but I've only seen this bug with Firefox.

Actual results:

When the window is resized, the content (both the page and Firefox's UI) is not updated to reflect the change. It just overflows to the bottom and the right of the window. It's fixed by restarting the browser. The visible content is still interactable and work as expected.

Expected results:

The window resize should cause the content to be resized.

Comment 1

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

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

Comment 2

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Hello, thank you for the bug report !
I tried to reproduce your issue but I was unsuccessful. Would you be so kind as to answer a few question so we can investigate this further?

• Could you please provide a screen recording/screenshot of the issue?
• Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
• Does this issue happen with latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
• Does this issue happen when Firefox is in Troubleshoot Mode? Here’s a link on how to enable it: https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-troubleshoot-mode

Comment 3

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Marking as RESOLVED INCOMPLETE due to the lack of answers from the reporter. Please re-open this bug if this issue is still reproducible on your side, thank you.