Closed
Bug 270449
Opened 20 years ago
Closed 19 years ago
firefox blocks requested popup when the function opening it is in a frameset
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: iquito, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.54 [en] Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 for your convenience you can test this bug on http://www.purplemoon.ch/ firefox_frameset.html and compare it to http://www.purplemoon.ch/firefox.html : The second page contains a link which opens a popup, firefox doesn't block this popup because it is (correctly) user-requested. The first page however contains a frameset in which you can click on the same link in every frame, the link opens the same function as before, just this time it is located in the frameset, so it calls the link javascript:top.last_messages() instead of javascript: last_messages() - firefox blocks this popup as an unwanted popup. Clearly, it isn't an unrequested popup and should not be blocked. Reproducible: Always Steps to Reproduce: 1. Go to http://www.purplemoon.ch/firefox_frameset.html 2. Try to click on any of the two links when having the popup-blocker enabled. For comparison see http://www.purplemoon.ch/firefox.html which contains almost the same code in a single html-file and which works flawlessly. Actual Results: Firefox blocks the requested popup-link you clicked on. Expected Results: It should have opened the popup because it was user-requested and not unwanted.
Comment 1•20 years ago
|
||
I'm experiencing the same bug. When I try the test case above, i can't reproduce this bug, howeven, in my university's WebCT application I experienced exactly the same behavier: When I'm in a page that is inside a frameset, and I click a button that is supposed to popup a new window, the popup is blocked, and I get a 'qwin has no properties' error on that javascript line. (qwin is assigned the result of window.open). The big problem is that the popup is blocked without a yellow bar to notify me, so I can't know that anything was blocked. Secondly, the popup shouldn't have been blocked since I clicked the button that caused it. When I access the same page without the frameset, the popup is still blocked, but now I get a yellow bar and I can unblock it.
Comment 2•19 years ago
|
||
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/
Comment 3•19 years ago
|
||
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•