Closed Bug 191939 Opened 23 years ago Closed 22 years ago

Pop-up blocker doesn't work properly, also need to have it so it can block ALL

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: yourking2, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 The pop-up blocker is not working properly. When I choose a site to block and the hit the refresh, the pop-up still comes up. It should also have the feature to BLOCK ALL pop-up sites!. Reproducible: Always Steps to Reproduce: 1.I go to the site 2.Then choose TOOLS/Pop-up Manager/Block Pop-ups from this site 3.Then it confirms 4.I then hit REFRESH upon that website and the pop-ups continue coming up 5.I've also tried removing Cache (mem and disk), and exiting Mozilla 6.Then I return to that website and the pop-ups come up again. Expected Results: It would be wonderful if this would work. Also, it should also have the ability to BLOCK ALL sites with pop-ups. Thank you!
> It should also have the feature to BLOCK ALL pop-up sites! Preferences > Privacy and Security > Popup Windows > "Suppress Popups"
The pop-ups denied not sticking sounds like a dupe of bug 190371, which was fixed on 1/29. Have you tried a current build?
Depending on the URL (which is lacking in this report), different methods are used to get around the pop-up blocker. 1) document.write (bug 187255) 2) window.open (bug 193872) there may be others, but these 2 seem to be the most prevalent...
Popup-blocking is whitelist based now, rather than blacklist. Marking WFM. Reporter, if there are specific sites you encounter where popups are not blocked but should be, please reopen this bug with links (making sure they aren't based on the two methods cited in comment 3).
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.