284427 - Popups blocked after a period of time

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Brent]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

This site uses popups to display new incoming messages, new people coming online
etc.

After a period of time, the notice comes up saying "Firefox prevented this site
from opening a popup window.  Click here for more options..."

The site is in the allowed list, but even if the popup blocking option is OFF,
the error will still occur.

To rectify the problem, it is necessary to shut down all instances of Firefox,
and restart a fresh window - where it will continue to work for a period of time
and then again start blocking the popups.



Reproducible: Always

Steps to Reproduce:
1.Log into Gaydar website
2.Wait for a 'period of time' allowing several popups to be displayed correctly
3.Popups will stop with 'Firefox has blocked...' error

Actual Results:  
Popups were blocked after a period of time of popups being displayed correctly

Expected Results:  
Continued allowing popups on the site

Have installed Firefox on 5 different machines, both version 1.0 and 1.0.1,
standard install - no themes, plugins, etc.

Comment 1

[OstGote!]

I guess you see it after ~ 20 popups (the default value for the pref
dom.popup_maximum), right?

Comment 2

[Brent]

Possibly starts after ~20 popups being displayed, but I think it could be more
than 20.

It is *possibly* ~20 per 'source' window - I can't confirm this however.

Comment 3

[OstGote!]

Yes, ~20 popups per site. I guess this is a duplicate of Bug 260264.

Comment 4

[Bugzillaatmozillaorg_5ehdbnz]

It still appears in version 1.0.2 on my machine.
Mozilla Firefox 1.0.2, Copyright (c) 2004 mozilla.org
It blocks also the Popups requested after clicking "Show blocked Popup" from the
popup notification related menu.

So then turning on the blocker and adding the site to the allow-list will help
to work around the problem.

Comment 5

[neil]

I'm getting the same behaviour with FF 1.03 . 

"So then turning on the blocker and adding the site to the allow-list will help
to work around the problem" - this doesn't make any difference.

Comment 6

[Gervase Markham [:gerv]]

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/

Comment 7

[Gervase Markham [:gerv]]

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.