Closed Bug 1830426 Opened 3 years ago Closed 3 years ago

Full screen bug on macOS

Categories

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

Firefox 112
Unspecified
macOS
defect

Tracking

()

RESOLVED DUPLICATE of bug 1829403

People

(Reporter: nick.star3m, Assigned: bradwerth)

Details

Steps to reproduce:

Open Firefox and stretch the browser window to fill the screen.

Then try to open and close Firefox in full screen. (⌘ + ⇧ + F)

Software Details:

Mozilla Firefox 112.0.2 (64 bit)
macOS Catalina 10.15.7

Actual results:

Browser window is now broken.

Expected results:

Browser window should close normally from full screen mode.

By the way, this bug only starts to appear in version 112.0.1.

And I already sent a request about this bug, but the developer could not reproduce it.

https://bugzilla.mozilla.org/show_bug.cgi?id=1829212

Component: Untriaged → General
OS: Unspecified → macOS
Hardware: Unspecified → All
Hardware: All → Unspecified

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

Component: General → Widget: Cocoa
Product: Firefox → Core
Severity: -- → S3
Priority: -- → P3

I can't reproduce this -- fullscreen can be entered and exited just fine for me -- but I can see some strange behavior that may be related. When I use Nightly and extend the window to fill the screen, it's also possible to make it stretch off the left side of the screen a bit, so just the green traffic light button is visible. Then when I toggle to fullscreen and back, I get this pattern:

  • first time go to fullscreen then exit fullscreen : window is resized to exactly fill the screen space
  • second time go to fullscreen then exit fullscreen : window is back to its original size with the left side of the window extended beyond the screen

And the cycle will continue that way. That doesn't make any sense and we should always be restoring to the original window size. I'll build a patch that fixes that and ask you to re-test with Nightly.

Assignee: nobody → bwerth

Also, are you using multiple monitors? If so, is the Firefox window on the same screen that has the menubar or on the secondary screen?

Flags: needinfo?(nick.star3m)

(In reply to Brad Werth [:bradwerth] from comment #3)

I can't reproduce this -- fullscreen can be entered and exited just fine for me -- but I can see some strange behavior that may be related. When I use Nightly and extend the window to fill the screen, it's also possible to make it stretch off the left side of the screen a bit, so just the green traffic light button is visible. Then when I toggle to fullscreen and back, I get this pattern:

  • first time go to fullscreen then exit fullscreen : window is resized to exactly fill the screen space
  • second time go to fullscreen then exit fullscreen : window is back to its original size with the left side of the window extended beyond the screen

And the cycle will continue that way. That doesn't make any sense and we should always be restoring to the original window size. I'll build a patch that fixes that and ask you to re-test with Nightly.

Strangely, this appears to be standard macOS behavior, reproducible in any application. So "fixing" this is unlikely to be part of the solution.

Hello, Brad.

I made a short video showing all the steps to follow to get this bug.

I uploaded it to YouTube: https://youtu.be/tTCpzQ8wpmI.

Hope this helps you to reproduce and fix this bug.

nick.star3m, now that the proposed fix in Bug 1829403 has landed, would you please try to replicate the issue with an updated Nightly build?

(In reply to Brad Werth [:bradwerth] from comment #7)

nick.star3m, now that the proposed fix in Bug 1829403 has landed, would you please try to replicate the issue with an updated Nightly build?

Sure. I just tested it on Firefox Nightly and it works well now. It looks like the problem is solved. Thank you!

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1829403
Resolution: --- → DUPLICATE
Flags: needinfo?(nick.star3m)
You need to log in before you can comment on or make changes to this bug.