Closed Bug 66799 Opened 24 years ago Closed 23 years ago

window.open with height/width from a maximized window makes the new window become maximized if you minimize and restore it.

Categories

(Core :: XUL, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 98701
Future

People

(Reporter: ruairif, Assigned: danm.moz)

References

Details

(Keywords: helpwanted, testcase)

Attachments

(1 file)

Okay, steps to reproduce:

1) Open a window with window.open. Set a width and height
2) Minimise all windows currently open by pressing 'windows key and a' or right
clicking the taskbar and selecting 'minimise all'.
3) Click on this window in the taskbar. It will reopen and fill the screen
rather than return to its original height and width

IE5 handles this correctly.
Using build 2001012604 on WinNT4
Yep I see that on 2001012708 trunk Win98.
Altough I don't think Javascript Engine is the correct component.
Maybe XP Toolkit/Widgets ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Browser, not engine. Reassigning to XP Toolkit/Widgets for further triage. 
Cormac F, could you attach a reduced testcase ("Create a new attachment" above). 
That will speed things along -  thanks -
Assignee: rogerl → trudelle
Component: Javascript Engine → XP Toolkit/Widgets
QA Contact: pschwartau → jrgm
I don't see this at all 2001012809, win2k. What are the steps to reproduce?
window.open with what arguments? Set a width: manually or in the arguments?
Steps to reproduce:

1. Maximize a Navigator window.
2. In that window, type in this URL to open a small new window:
     javascript:void(window.open("","","width=100,height=100"));
3. Right-click the Windows taskbar and select "Minimize All Windows"
4. Click on the icon for the new window in the Windows taskbar.

Result:          new window reappears maximized.
Expected result: new window reappears at the same size that it had before.

Alternatively, add "resizable=yes" to the window.open string and just minimize 
the new window for step 3.

Mozilla 2001 012708 on Win98.
Summary: Minimize then maximize a window.open window ignores height and width values → window.open with height/width from a maximized window makes the new window become maximized if you minimize and restore it.
->danm for triage. Is that a magic size, or will any size cause it?  Are users
likely to encounter problems due to this?
Assignee: trudelle → danm
Any sized window can trigger this bug (100x100 isn't a magic size).
If I remove the width/height: javascript:void(window.open("","",""));
I get a large window that covers the entire screen, including my Windows 
taskbar.
->future/helpwanted
Keywords: helpwanted
Target Milestone: --- → Future
*** Bug 72416 has been marked as a duplicate of this bug. ***
Win98 2001031604

Additional window.open bugs what might be related to this bug:
(All based  on example of http://www.laser-jama.nl/high_resolution.html)
1) screen.height and screen.width are reporting wrong values=new window does 
not want to fit to screen resolution despite this script does a little reducion 
of these values (click on any icons on that page and You see.);
2) Select "minimize all windows" from taskbar menu and then select "undo 
minimize all", this new window will occupy whole screen or will be over screen 
borders, even taskbar is covered even it is set to "always on top";
3) Drag this window to place or move it a bit, try now select "minimize all 
windows" - all the other windows are minimizing, but not this one. 
Ivo: 2 and 3 sound related but 1 sounds like a separate bug.
*** Bug 74305 has been marked as a duplicate of this bug. ***
*** Bug 71900 has been marked as a duplicate of this bug. ***
I'm seeing this on 2001052109/Linux/enlightenment-0.16.5-5mdk. Happens all the
time at http://www.mstraffic.com (click on the "Traffic Cameras" link and then
click on one of the camera images on the map). This page uses a function with
the line:

OpenWindow=window.open('showCam.htm?cam=' + nmbr, 'cam',
'height=450,width=350,toolbar=no,scrollbars='+scroll+',menubar=no');

This window sized itself OK with 2001051709. Maximizing the window seems to have
nothing to do with it, AFAIK.
*** Bug 82432 has been marked as a duplicate of this bug. ***
Could this be because all newly spawned browsers are refering to the initially
opened browsers current state?

Shouldn't all newly spawned browsers refer to the initially opened browsers LAST
RESTORED state?

*** Bug 88707 has been marked as a duplicate of this bug. ***
Jessie,

I agree 88707 is similar, but the behavior described in 88707 has NOT been
addressed in 66799. Bug 88707 adds the bug on initial opening of the window.open
popup takes on the current state of the opener. Is this related? yes, is it a
duplicate? I don't know.

Greg: are you referring to the way the new window has a "restore" button instead
of a "maximize" button in the title bar?  I think that's covered by this bug,
which is really about the new window being in a strange state after being opened
from a maximized window.  (The window having the wrong button was mentioned in
bug 82432, which is also marked as a duplicate of this bug.)
If its covered, i missed it. I just wanted to add that the resore/maximize 
wigit issue follows a pattern. If the initial browser is maximized, so will the 
window.open when invoked, if initial is in restore state, so will the 
window.open when invoked.

I'm beginning to believe this is NOT a wigit issue but a browser issue and 
heres why... 

here is a related problem to add to the list.

1.create new window using window.open()
2.Close all other browser windows (NOT the window.open)
3.go back to the desktop and open a new instance of the Mozilla browser

result: Browser will invoke itself in the window.open window
expected result: All new browsers opened with the program link should create a 
new instance of the browser.
 
I've been browsing using mozilla for quite some time now and this bug is
becoming increasingly more obvious. Blame it on the "economic downturn" or
whatever, but many of the most popular sites are increasingly using pop-up ads
on their main pages. Mozilla opens these windows and, in many cases, instantly
expands them to fill the whole screen.
As an example, go to one of the more popular film sites - http://www.aintitcool.com
Every time the main page is loaded, a small pop-up window appears. This
immedaitely resizes itself to fill the screen, making this site extremely
irritating to use.
Someone should, I imagine, increase the severity of this bug and target it for a
pre-1.0 milestone?
I just read through this bug again, and I'm not sure what is supposed 
to be fixed here, and what may be irrelevant (7 months since the bug 
was filed). There are multiple recipes for illustrating completely
separate behaviours. 

Note: the most recent comment describes something that is a known problem,
was fixed by a one-line JS change for the 6.1/0.9.2 branch, will be fixed 
one way or another for 0.9.4, but a more complete solution is being considered.
See bug 91884.
With build 2001091003 on Win2k, clicking the link in above attachment gives me a
maximized window. IE6 and previous Mozilla releases did open a small window as
expected. This is the testcase from bug 99265. btw, should I mark bug 99265 a
dupe of this one ?
Keywords: testcase
hmm, bug 99265 became a dup of bug 98701, which had a working fix checked in 
for it today. And, with that, we say goodbye to this bug based on the LIFO
technique for bug definitions. If there is some behaviour in the variety of 
statements above that is still apparent in current builds, then please do file 
it as a new [or new-old] bug. 

*** This bug has been marked as a duplicate of 98701 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
VERIFIED Dupe
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: