Please report any other irregularities here.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 We have an internal application that uses popup screens for a variety of functions. In order for our application to work properly, we have to configure FF to allow popups from the application's site, which at first, seems to work fine. The popus appear as expected. I have noticed that, after extended periods of use (several hours and the appearance of maybe 100 or more popup screens), I eventually encounter the message that "Firefox has prevented this site from opening a popup". If you click the "Options" button, the options available seem to indicate that poups are already allowed fromn this site (which they are). If you look at the list of sites from which popups are allowed, the application site is still listed. However, no popups are allowed from that site anymore. The browser will continue to operate in this manner (blocking all popups) until FF is closed and restarted, at which time the cycle begins again. This condition has been observed on all released versions of FF since 1.0.0, and still occurs on 1.5. This condition does not occur on the current release of Mozilla (1.7.11) nor has it been noticed on any of the previous releases. For this reason, I have been primarily been using the Mozilla browser instead of FF when accessing our application. Reproducible: Always Steps to Reproduce: 1. See "Details" 2. 3. Actual Results: FF eventually starts blocking popups from sites that have been configured to allow popups. FF continues to block popups until browser is shutdown and restarted. Expected Results: FF should allow popups from all sites that have been configured as such, as long as the browesr is operating. This condition happens in all releases of FF since 1.0.0. This condition has never been observed in any release of Mozilla.
There is a hard limit of 20 popups per window, though it should only be triggered for simultaneously triggered popups. Could you try setting the dom.popup_maximum pref to a high number using about:config and see if that solves your problem?
(In reply to comment #1) > There is a hard limit of 20 popups per window, though it should only be > triggered for simultaneously triggered popups. Could you try setting the > dom.popup_maximum pref to a high number using about:config and see if that > solves your problem? > I changed it to 500. I'll start using FF again to access our application exclusively and see if the condition goes away. Thanks for the recommendation. gmc
Summary: Popup blocker seems to stop[ working properly after extended period of use → Popup blocker seems to stop [working properly after extended period of use]
Version: unspecified → 1.5 Branch
Summary: Popup blocker seems to stop [working properly after extended period of use] → Popup blocker seems to stop working after many popups have been opened (extended period of use)
We are having this same problem. We have a web application that requires a regular popup notification. It starts getting blocked after 20 times even though the site is in the browsers allow popups list. It shouldn't ever block popups from a site in the allowed list. It is unacceptable to make our users change this setting. You say it should only be triggered for simultaneously triggered popups. What constitutes a simultaneously triggered popup? Once we hit the 20 time limit, there seems to be no way to reset it.
This seems like a duplicate of bug 260264 to me. Reporter, do you agree?
This bug was reported using a version of Firefox that security and stability updates are no longer provided for. All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'. If you can still reproduce this bug, please provide additional details to help resolve this issue.
No reply, INCO. Please try to reproduce with firefox 3.5.3 or later in a new profile.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.