Closed
Bug 253155
Opened 20 years ago
Closed 19 years ago
Securety icon cover Popup Blocker one
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: gsbarbieri, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 When using https, the locker icon is placed where the popup icon was supposed to shown, leting users to get the impression the web site isn't working, when it is, but the windows were blocked. Many web banks use popup windows and this is bad to firefox users, since firefox came with popup blocker active by default. Reproducible: Always Steps to Reproduce: 1. Access a secure http site 2. Activate a javascript that calls window.open() 3. Look at the bottom-left, there's only the "locker icon". Expected Results: There should be two icons, one for the popup blocker and other for the secure connection.
Comment 1•20 years ago
|
||
Please, give us an URL to test what you mean. Thanks.
Reporter | ||
Comment 2•20 years ago
|
||
http://gustavo.ltc.ic.unicamp.br/test-firefox-bug.html Additional Information: When I received the mail asking for an URL I started to investigate and discovered the problem is else where: It's not the "locker icon" that was covering the "popup blocker icon", but the net banking site that was using a weired combination: window.open( url ) history.go( -1 ) What happens is the desired icon flashes (appear and go away). This happens due the history.go() command. I don't see a clear solution to this bug. If it's possible, leave the popup blocker icon after the page is leave. But this will lead to the icon always being displayed... Another solution would be to keep the icon if the domain is the same or if the page was redirected using history.go(), parent.url, ... or some other javascript resource. Thanks for the quick reply. Gustavo
Comment 3•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 4•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
•