Javascript window is unresizable by user



16 years ago
14 years ago


(Reporter: aadudek, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)





16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Go to search for store availability on Maxtor 40 GB, type in zip code 20147,
results come up but you are unable to view. I have disable the ability for
scripts to Move or resize, raise or lower, and hide the status bar. I have also
seen a similar problem with javascript calander. It is on an internal website so
I cannot post a link, but even with allowing the script all permissions, when I
change the month, the calander disappears and never comes back. I maybe able to
provide the code for the javascript if needed.

Reproducible: Always

Steps to Reproduce:
1.Go to search for store availability on Maxtor 40 GB
2.type in zip code 20147

Actual Results:  
Results came up but was unable to move window to allow viewing.
Also, changing the month on a javascript calander, the calander does not reload
in the window.

Expected Results:  
Scroll bars to appear on left side to scroll window down or allow for user to
resize window.
Also to show the new month when changing the month in javascript calander and
allow window to be scrolled or resized by user.

I have disable the ability for scripts to Move or resize, raise or lower, and
hide the status bar.
With the calander issue, it doesn't matter whether full permissions is on or not.

Comment 1

16 years ago
Website with calander code... Same problem as reported on private website
Change current month to next and javascript popup does not reload calander.

Comment 2

16 years ago
Reassigning to Browser-General until we can get further information.


1. In order to eliminate user preferences as the cause,
please create a new profile and run Mozilla under it:

  Tools > Switch Profile > Manage Profiles > Create Profile

Do you still see the bug under the brand-new profile?

2. Also, please try an up-to-date build in case that might be the cause.
We are beyond version 1.4 now; thanks -
Assignee: rogerl → general
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → general

Comment 3

16 years ago
Creating a new user profile did fix the first problem associated with Bestbuy page.
It did not fix the problem with the Javascript calander. I will try 1.5 Alpha
and see if it fixed. 

Comment 4

16 years ago
I have verified that the Javascript Calander program still does not work under
1.5a (build 2003971814)


Comment 5

15 years ago
Cannot reproduce on Mozilla 1.7 RC 1 (build 2004042109) on Win98SE
even with move and resize windows, etc. preferences disabled
Product: Browser → Seamonkey
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.