365776 - The dialog indicating that I have connected to a secure site never appears

Status: RESOLVED INCOMPLETE

(Firefox :: Security, defect)

Description

[ngatsiou]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

 There isn't any warning dialog. The lock in the low right appears locked, as it is supposed to be. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
This problem happens every time


Microsoft XP Build 2600, Bios Phoenix Technologies  2.3 , Greece, 512 MB ram,  amd 3500 64 bit

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

No problem, as you can see on this screenshot: http://img301.imageshack.us/img301/5659/naamloosxz5.png (and if this is what you mean).
You could try changing security.warn_entering_secure.show_once to false in about:config: http://kb.mozillazine.org/About:config

Comment 2

[Jesse Ruderman]

What warning did you expect to see?

Comment 3

[ngatsiou]

I changed the security warn entering show.once to false, but the problem remains.
Yes thats what i mean. I don't get the warning dialog that you show in your screenshot..

Comment 4

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.