popups not allowed from a site with a non-standard port number

RESOLVED EXPIRED

Status

SeaMonkey
Preferences
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: wsloand, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316

When I'm using gallery on my site, which is running off port 8080, it blocks the
popups.  After the popup is blocked, I try to unblock it (via the icon at the
bottom of the window), add my site (with port number as it is listed) to the
list.  When I try again, my site is still there, but without the port number and
the popup is blocked.

Note:  popups only happen in admin mode with gallery.

Reproducible: Always
Steps to Reproduce:
1. Go to my gallery
2. Try to load an admin page (popup is blocked)
3. Add my server (with port number) to allowed popup pages
4. Try to load an admin page again (popup is still blocked, server name is on
the allowed list without the port number)
Actual Results:  
The popup is blocked, and the server (without port number) is on the list

Expected Results:  
The popup should have displayed, and the server with port number should be on
the list
(Reporter)

Comment 2

14 years ago
Upon later trying it appears to be a flaky problem, and I can't isolate the
situation (it has only happened a couple of times out of very many)

Comment 3

14 years ago
I'm guessing I have to be you before I can see the mysterious admin page. So I
can't even attempt to reproduce the bug as written. I do know this: since bug
200644 was checked in, the port number should simply be ignored.
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:
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: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.