414454 - webpage tries to maximize already maximized browser window

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[martin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b3pre) Gecko/2008012704 Minefield/3.0b3pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b3pre) Gecko/2008012704 Minefield/3.0b3pre

(these steps trigger the bug on windows only, linux works just fine)

1. open this url:  http://reddit.com/info/66uxr/comments/
2. maximize the browser window
3. right-click the main link titled "A380 cockpit (OMG!)" and select "open link in new window"

Expected results:
The A380 page should load in a new TAB of the already maximized window.

Actual results:
A cheezy script on that page explicitly sets the size of the browser window with the intention of "maximizing" the window size. But my window is already maximized so the net effect is that my window goes from "cleanly maximized" into "a 'non-maximized' window which has the same size as the screen". This is extremely annoying, and it also affects all the other pages I have loaded in other TABs and when I open new windows they are "as big as the screen but still not maximized". Yuck!


Some kind of sanity is required here. I'm not sure what the javascript standard says about this behavior if it does say something explicit. I would rather like ff to just stay maximized if a javascript tries to set window size to screen width/height while the window is already maximized.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Ria Klaassen (not reading all bugmail)]

That is, because you are allowing scripts to "move or resize existing windows" in Tools -> Options -> Content -> Advanced JavaScript Settings. When I uncheck this option, the size of the window can't be changed anymore by scripts.
See also Bug 412862.

Comment 2

[Tyler Downer [He/Him]]

Does this still happen in firefox 3.6.6 or later in a fresh profile?

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.