Closed Bug 247462 Opened 22 years ago Closed 20 years ago

ssl icon overwrites the popup blocking icon on lower left in the browser

Categories

(Firefox :: General, defect)

1.0 Branch
x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: shao, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 When visiting a ssl site that opens a popup, the ssl security icon will overwrite the popup icon. You can actually see the popup icon first, then it gets overwritten. This makes impossible for user to select the popup icon and unblock the window if desired. User must maually go to options and add the url. What is worse is that from the example given, the website actually redirects to a different address, so it is very hard to capture the original url. Reproducible: Always Steps to Reproduce: 1. enable popup blocking in mozilla or firefox 2. go to http://www.stgeorge.com.au 3. click on Log onto internet banking Actual Results: 1. popup blocking icon appears as the login window is blocked 2. the icon is overwritten by ssl icon as the website redirects to another https address 3. at this stage, a novice user must be very confused. Expected Results: Both popup blocking icon and ssl security icon should appear in lower left. I actually saw it working around firefox 0.6 days.
When you navigate away from the page that triggered the popup , the popup blocked-icon will automaticly go away too. This is perfectly normal. "Not a bug - a feature"
Product: Browser → Seamonkey
Assignee: general → firefox
Product: Mozilla Application Suite → Firefox
QA Contact: general → general
Version: Trunk → 1.0 Branch
This has all changed a lot since the bug was filed. I think this is now WFM, but I could be wrong (perhaps invalid). I'll WFM - alter if you disagree!
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.