Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

[macOS/osx] Always open new windows maximized

  • 1 reply
  • 2 have this problem
  • 54 views
  • Last reply by Wojtek

In a nutshell - how to make firefox always open new window (or restore recently closed one) in maximized state (i.e. using all desktop, but not fullscreen)? The dimensions seems random at best, usually using half width and about 85% height positioning it in... random places on the desktop. What's more, restored windows don't remember the size they had just seconds ago! Under windows you could modify shortcut properties and set "always start maximized" but this only applied to cold-start and single window and... MS Windows.

Is there an option to make firefox always maximize window? Or should I file a bug?

In a nutshell - how to make firefox always open new window (or restore recently closed one) in maximized state (i.e. using all desktop, but not fullscreen)? The dimensions seems random at best, usually using half width and about 85% height positioning it in... random places on the desktop. What's more, restored windows don't remember the size they had just seconds ago! Under windows you could modify shortcut properties and set "always start maximized" but this only applied to cold-start and single window and... MS Windows. Is there an option to make firefox always maximize window? Or should I file a bug?

Chosen solution

OK, this was actually caused by setting `privacy.resistFingerprinting` to `true`

Relevant bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1402557

Read this answer in context 👍 0

All Replies (1)

Chosen Solution

OK, this was actually caused by setting `privacy.resistFingerprinting` to `true`

Relevant bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1402557