VOOZH about

URL: https://bugzilla.mozilla.org/show_bug.cgi?id=471940

⇱ 471940 - viral site hijacks firefox with unkillable pop-ups


Closed Bug 471940 Opened 17 years ago Closed 17 years ago

viral site hijacks firefox with unkillable pop-ups

viral site hijacks firefox with unkillable pop-ups
Firefox
Security
unspecified
x86
Linux
defect
Not set
major
Points:
---
RESOLVED DUPLICATE of bug 59314
RESOLVED
DUPLICATE
of
Iteration:
---
a11y-review
Accessibility Severity
Performance Impact
Webcompat Priority
Webcompat Score
Tracking Status
relnote-firefox
firefox-esr115
firefox-esr140
firefox-esr153
firefox152
firefox153
firefox154
---
QA Whiteboard:
---
Has STR:
---
Change Request:
---
Bug Flags:
Signature:
None
This bug is publicly visible.

 
Reporter

Description

17 years ago
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Fedora/3.0.5-1.fc10 Firefox/3.0.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Fedora/3.0.5-1.fc10 Firefox/3.0.5 If I browse to http://scan4new.com/22/?uid=114 I get a fake Windows desktop which pretends to be scanning my C drive and recommends downloaing some malware. It keeps popping up pop-ups. It is impossible to kill all the pop-ups. The only way to kill it is to force-kill firefox. Making this worse is that when the pop-up is active I cannot switch to another tab - the entire UI is unresponsive until all the pop-ups are closed - which is impossible. It seems a fundamental bug if a pop-up windows can disable the entire Firefox UI - no menus work, clicking in a tab doesn't work, closing the firefow window doesn't work. This is unacceptable. Another suggestion: Perhaps the "Stop loading this page" button could be dual-purposed to stop an JavaScript running in the current tab/window? Reproducible: Always Steps to Reproduce: 1. 2. 3.

Comment 1

17 years ago
fwiw, I could close that tab with Ctrl-W while hitting Enter to close the alerts.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.