User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:18.104.22.168) Gecko/2008102920 Firefox/3.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:22.214.171.124) Gecko/2008102920 Firefox/3.0.4 I use this website which shows popups when messages arrive. I don't like this option so I have set the firefox popup blocker on to make sure these popups aren't shown. When I open the page-settings dialog to print the page I'm viewing, the popups do pop up (the page refreshes in regular intervals) where they should still be blocked. It might be the same in other dialogs, haven't tested it. Reproducible: Always Steps to Reproduce: 1. Use a website that refreshes itself regularly and that opens a popup 2. Make sure that website is blocked in the popup blocker 3. Open the "page-settings" dialog in the file menu and wait for the page to refresh. Expected Results: The popups should have been blocked I believe this might have security consequences
The popup blocker is an anti-annoyance feature. Extra popups are unwanted but not a security exploit that needs to remain hidden. We'd probably be able to diagnose this quicker if you provided a link to a site that exhibits the problem. The popup blocker tries to walk a fine line guessing which popups you really wanted (clicking on a button or link that pops up a detail image, for instance) and which ones are unrequested. Maybe opening the page settings dialog is incorrectly interpreted as one such action.
Dupe of bug 463491, if not something earlier. Handy STR: 1. Load http://www.auditmypc.com/freescan/popup/popup-test.asp#popup-test 2. Click the link to start the test, and quickly 3. Ctrl+P for the print dialog, or Ctrl+S to save
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days. Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to RESOLVED, WORKSFORME.
Problem is gone in 3.6.10