Main window not maximized if fullscreen toggling done and Firefox reopened

NEW
Unassigned

Status

()

11 years ago
4 years ago

People

(Reporter: wxpythoner, Unassigned)

Tracking

Trunk
All
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

The main window of Firefox is not maximized if fullscreen toggling was done and Firefox was reopened.

Reproducible: Always

Steps to Reproduce:
1. Start Firefox and have ONE Firefox's window opened and MAXIMIZED.
2. Now press the F11 button on your keyboard to view the page fullscreen.
3. Press the F11 button again to exit the fullscreen view.
4. Now exit Firefox.
5. Open Firefox again and see that you don't have the window maximized
   anymore, but you should've had.



This is a regression bug of Firefox for Windows OS.

Note: I've tested this bug in Firefox 3.0 Beta 4 for Linux in Ubuntu 8.04 Beta and the bug was not reproducible there.

This bug should be fixed!

Updated

11 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
still valid for
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090316 Minefield/3.2a1pre ID:20090316044350

workaround is minimizing (not changing focus with other app!) Fx before exiting Fx.

maybe related to Bug 423641?

Comment 2

9 years ago
similar like bug 454348 ?

Comment 3

4 years ago
For me the issue is not related to restarting Firefox, but it just does not restore the "maximized" properties (_NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ) when leaving fullscreen mode (and unsets them before going to fullscreen).

See https://github.com/awesomeWM/awesome/issues/245 with more details.

Comment 4

4 years ago
This is with Firefox 38 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0)
You need to log in before you can comment on or make changes to this bug.