Closed Bug 238343 Opened 22 years ago Closed 20 years ago

popups blocked even if domain added to exception list

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: lohphat, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040322 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040322 See below Reproducible: Always Steps to Reproduce: 1. Goto test link 2. Enter "cnn.com" into first field 3. Hit enter 4. See popup warning icon in status bar Yes, whois.net is in the exception list.
WFM. If i click in the icon, networksolutions.com is automaticly filled in. That's because that is the domain that tries to open the popup, not whois.net
Just enter the domain in the first text box and press enter, not the GO button.
Here's another example URL: http://www.marumushi.com/apps/newsmap/newsmap.cfm 1. Add site to exception list 2. Click on news headline 3. New window not opened
In addition, Ctrl-N does not open a new window either.
Can we generalise this as a flash plug-in issue?
gmail popups aren't working for me even though it's whitelisted... doesn't seem to have much to do with flash - no problems before upgrade to Firefox 1.0 PR - on 0.9.3 was fine. Haven't tried a clean profile yet. Can't open the blocked popup from the menu either...
Above (gmail) problem fixed by disabling Tabbrowser Extensions.
URL in Comment #3 now working. Clicking on news snippet opens in new window. 2004112005 win32
(In reply to comment #7) > Above (gmail) problem fixed by disabling Tabbrowser Extensions. Same problem as above. Extension list as follows: DOMI 1.0 NukeAnything 0.2 Google Pagerank 0.9 However, I suspect this is a change in gmail itself, since the popups were working yesterday and no changes have been done to the system.
Product: Browser → Seamonkey
In my case, *all* popups were blocked, even if "Block Popup Windows" was unchecked. And, indeed, disabling Tabbrowser Extensions was the culprit.
Reporter, does this work for you now for whois.net? If so, please resolve this bug.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.