Firefox blocks and cannot be launched anymore.




13 years ago
12 years ago


(Reporter: Raanan Barzel, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0

On a website relying on popups for its operation, if you click on a link which
uses a popup without enabling popups for this site, Firefox blocks. If you close
Firefox (system x button), a process remains active and does not allow to launch
Firefox again.

An experienced user may know how to kill the remaining process, but a normal
user should not be expected to go into task manager to solve this problem.

Reproducible: Always
Steps to Reproduce:
1. Go to, DO NOT ENABLE POPUPS. Scroll down and click on
"LES SPECTACLES EN VENTE". Firefox blocks. Mouse has no response within Firefox
2. Close Firefox with System 'x' button. 
3. Click on desktop Firefox icon to restart Firefox.

Same problem with other sites operating similarly.

Actual Results:  
Profile is in use and Firefox cannot be launched. 
Must open Task Manager and kill subsisting Firefox task.

Expected Results:  
When you close Firefox, you should be able to launch it again normally - e.g.
from desktop icon.

Standard install.
No themes.
No Extensions.
Windows Xp Home SP2.

Comment 1

13 years ago
as posted by wgianopoulos in

Confirm that the problem is solved in today's release.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041018 Firefox/1.0

WFM (but I have the "popupbar" disabled)

Open the page with popups blocked
rightclick on the "blocked" icon in the statusbar
select "allow popups for ""
reload page
and happily browse on
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: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.