User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 When an extension is set up to open up in a tab, most of the options in that extension's context menu no longer work. Sidebar and floating window options, however, are unaffected - All of the context menu options will work there. On further inspection, I have noticed that the options that do not work are also the ones that open up a new window, as the icon for the popup blocker shows up when the extension tries to open a new window from those particular context menu options (with the name of the extension's "chrome:" page in the list). Reproducible: Always Steps to Reproduce: 1. Install an extension that has a custom context menu (with at least one option in that menu that will open up a new window), and can also be opened in a tab. 2. Set up the extension so that it can be opened up in a tab. 3. Open the extension in a tab. 4. Right-click in the window for that tab to bring up the context menu for that extension. 5. Click on an option in the context menu that will create a new window. Actual Results: The new window opened from the extension did not appear, and the "Blocked Popups" icon showed up in the status bar. The extension's "chrome:" page is in the list of blocked popups. Expected Results: The new window opened from the extension should come up normally, without being blocked. Not all extensions seem to suffer from this problem - Of the ones I have installed, however, QuickNote is the only one I've spotted it in so far (though other extensions may be affected as well). I originally thought this was a problem with QuickNote, but after posting a bug report at MozDev [http://bugzilla.mozdev.org/show_bug.cgi?id=6904], I was told that this is a problem with Firefox (and recently, I have noticed that Mozilla is also affected by this - I was using Mozilla 1.7.1 at the time of testing). I got the same results regardless of whether I was using my current profile, or a brand new profile. The "Expected Result" can be produced if the blocked "chrome:" page is added to the list of sites allowed to open popup windows - But why are "chrome:" pages allowed to be blocked in the first place?
Actually, a Browser bug. See also bug 204328 (this one is not a dupe, IMO).
Changing to "browser" as it affects Mozilla Suite as well. Updating Summary to better reflect the problem.
Filter "spam" on "guifeatures-nobody-20080610".