Closed
Bug 276226
Opened 20 years ago
Closed 19 years ago
Instead of blocking a pop-up window spawned at www.usatoday.com, FF starts creating endless new window instances
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: reddogs, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 One particular pop-up window (for a mortgage company) spawned at www.usatoday.com seems to send FF into a loop with an infinite number of new pop-up windows being created faster than you can close them. The only way to stop this loop is to close the "parent" window (not easily done when your taskbar is now full of Firefox icons). Reproducible: Sometimes Steps to Reproduce: 1. go to www.usatoday.com 2. wait for mortage company pop-up to occur 3. Actual Results: Since usatoday.com seems to have a large array of advertiser pop-up windows that I believe are randomly spawned, it's impossible to consistently duplicate the problem. Expected Results: Blocked the pop-up ad or, at the very least, opened only one new FF window instead of endless FF windows.
Updated•20 years ago
|
Summary: Instead of blocking a pop-up window spawned at www.usatoday.com, FF starts creating endless new window instances → Instead of blocking a pop-up window spawned at www.usatoday.com, FF starts creating endless new window instances
Comment 1•19 years ago
|
||
I have opened http://www.usatoday.com/ with Firefox 1.5.0.3 ID:2006042618 on WinXP sp/2 and it seems no further pop-ups are launched by this site. Gaye - if you can provide source code to see how these pop ups were launched earlier, this problem might be tackled. Please do report back if this is the case! Otherwise, this specific bug as a problem with the page usatoday.com is a WORKSFORME. Cheers, Cigno
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•