Closed
Bug 111545
Opened 23 years ago
Closed 3 years ago
script that tries to "almost maximize" an already-maximized window unmaximizes it
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: aufbau01, Unassigned)
References
()
Details
(Keywords: parity-ie, testcase)
Attachments
(1 file)
520 bytes,
text/html
|
Details |
Steps to reproduce: 1. Maximize your browser window. 2. Load the URL above (warning: porn) or the testcase. Actual result: In Mozilla: window unmaximizes. In Netscape 4: window unmaximizes and then re-maximizes. In Internet Explorer: window unmaximizes and then re-maximizes. In Opera: window moves to the middle of the screen but is still in a maximized state. Expected result: window should remain maximized the whole time. Note that in all browsers I tested, resizeTo/moveTo could not turn a normal window into a maximized window. Netscape 4 and Internet Explorer seem to remember that the window was once maximized. (I'd prefer if webpages didn't try to resize themselves, but many porn sites do try to "maximize" themselves by becoming as large as they can.)
Reporter | ||
Comment 1•23 years ago
|
||
Comment 2•22 years ago
|
||
just turn if off if you dont like it :P
Sizing a maximized Mozilla window unmaximizes it. Otherwise windows opened to a specific size from a maximized browser window would themselves be maximized, to the great annoyance of all. Think popups. See bug 98701 and bug 43001. Personally I'd be more annoyed by that than by losing my maximized state in a legitimate browser window. I choose to stick with the current behaviour. Bug 98701 is a dead snake. If you're bothered by websites which resize your window on you, you can disable their ability to do that in edit > preferences > advanced > scripts. It's a shame users have to do that, but the web is full of jerks.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 4•22 years ago
|
||
Reopening. * This bug is only about what happens when an already-maximized window tries to resize itself to dimensions larger than the screen can hold. * Mozilla's behavior does not match IE's behavior and does not match Netscape 4.x's behavior. In both IE and Mozilla, resizing an already-maximized window to dimensions larger than the screen temporarily resizes it and re-maximizes it. (On my Windows XP machine, these things happen so fast that I barely notice them, and a reasonable improvement over IE's and 4.x's behavior would be to skip the step of temporarily resizing the window.) * Mozilla's behavior does not match what the web site is trying to do, which is to make itself as large as it is allowed to make itself. * Fixing this bug would not necessarily allow a web site to maximize itself if it is not already maximized. (See IE's and NS4's behavior.)
Severity: minor → normal
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•22 years ago
|
Summary: Mozilla unmaximizes a page as it tries to fill the screen (resizeTo/moveTo) → script that tries to "almost maximize" an already-maximized window unmaximizes it
Comment 5•21 years ago
|
||
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs
Status: REOPENED → NEW
Comment 6•20 years ago
|
||
*** Bug 240152 has been marked as a duplicate of this bug. ***
Comment 7•18 years ago
|
||
i can confirm this bug (using the testcase) firefox 1.5, windows xp as workaround you can disallow scripts to "Move or resize existing windows" in the advanced javascript settings
Comment 8•18 years ago
|
||
Can you please fix this? As other browsers act correctly so should firefox. My homebanking page is affected by this and it´s very annoying. Thanks :)
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: amar → general
Comment 9•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-ie
Whiteboard: parity-IE
Updated•6 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 22 years ago → 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•