Closed Bug 593652 Opened 14 years ago Closed 14 years ago

pop up blocker not working

Categories

(Firefox :: General, defect)

x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 565104

People

(Reporter: edwardschwartz0916, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 getting a lot of pop ups, think they are called under pop ups, because they appear when I close the website. I am using the new firefox beta browser 4.0 Reproducible: Always Steps to Reproduce: 1.closed firefox windows 2.opened new website 3.found under popup when I closed original window Actual Results: same thing as before Expected Results: no more popupse
Group: core-security
This is not a support website, this is for filing bugs. http://support.mozilla.com/en-US/kb/Pop-up+blocker#Pop_ups_not_being_blocked It's actually quite normal, some popups can't be blocked without causing problems for regular websites, as it's difficult to see the difference between regular windows and the type you want to block.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Jo Hermans.....My pop-up blocker is checked enabled, and this problem never occurred in previous firefox versions, only the new beta...I don't know whether it's a support or bug problem, but someone should fix it.
Nothing changed in the popup blocker - it's the websites that have started to use them again. And most of them are pop-unders currently. Since a pop under is a type of popup that is most likely the kind that you don't want, there might be something to do here, without breaking any legitimate sites See bug 565104 and bug 502824 for more info.
Resolution: WORKSFORME → DUPLICATE
when all else failed, I looked at malware//spyware problems....removed an reinstalled my malware program (STOPZILLA), and ran a new scan...found a virus and a worm...computer is now running perfectly (atleast until the next incident occurs).
You need to log in before you can comment on or make changes to this bug.