javascript window does not resize when a second pop-up is clicked

RESOLVED EXPIRED

Status

()

Core
DOM: Core & HTML
--
minor
RESOLVED EXPIRED
15 years ago
4 years ago

People

(Reporter: noah luken, Unassigned)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

The example page contains two images that are different orientations.  Clicking
on the first image works as it's supposed to, but clicking on the second image
doesn't resize the popup window to the new image size.  

Reproducible: Always

Steps to Reproduce:
1. click on either of the images and see the popup come up (ignore the 'close' link)
2. click on the other image
3. notice the way that the pop up window has not resized and the new image is
cut off

Actual Results:  
see above -- the same window holds the same image, and cuts it off

Expected Results:  
either:
1) open another pop up image window (the correct size) for the second image
2) resize the existing pop up window to the dimensions of the second image

Please note:  I don't know whether this is actually a bug or how javascript is
*supposed* to work, since IE6 does the same thing. The 'expected results' above
are what, as a regular user, I would hope my browser would do: deal with
repeated javascript windows intelligently. 

This may be the fault of Javascript itself and out of your hands, and if so, I
hope I haven't wasted too much of your time.  Maybe this is actually a feature
request rather than a bug report.
There are no "windows" in JavaScript -- those are DOM.  :)

That said, this has been filed before, and marked WONTFIX, if I recall correctly....
Assignee: rogerl → dom_bugs
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → ashishbhatt
Whiteboard: DUPEME
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED

Updated

4 years ago
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.