258691 - Unable to re-enable security warning dialogs once disabled

Status: VERIFIED DUPLICATE of bug 252362

(Firefox :: Settings UI, defect)

Description

[brian]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

The default option on many of the security warning dialogs is to disable that
warning.

For example the security warning "You have requested an encrypted page..."

If the warning is disabled, there is no place to turn the warning back on again.

Users (like myself) sometimes simply hit enter when they expect a warning and
don't read the whole text.  If the checkbox does not get filled in on the very
first occurrence of the warning box, that warning is gone forever.

If there is a place to re-enable these warnings, it is not obvious and is not in
the help file.

The obvious "work around" is to never click without reading, but we're only human.


Reproducible: Always
Steps to Reproduce:
1. install firefox .9
2. visit an SSL protected site
3. click OK without filling in the checkbox

Actual Results:  
Security Warning Dialogs were disabled and there is no documented place to turn
them on again

Expected Results:  
A documented place should exist to re-enable the Security Warning Dialogs.

Comment 1

[Gonzalo HIGUERA DÍAZ]

Workaround:

1.- Type "about:config" in the URL bar.
2.- make "security.warn_entering_secure.show_once" equal to "true".

The dialogue will show up again and you can check the box to make it available
in future times. Similar security dialogues can be set up to be show again with
the "security.warn_*.show_once" settings.

This workaround does not set aside the question of whether a dedicated menu to
set these parameters should be in the default build or not. Is it a policy
compatible with Firefox's aims to become a reference browser not to offer a way
to easily set its security features?

Comment 2

[Gonzalo HIGUERA DÍAZ]

This can be considered the same as bug 257233.

Comment 3

[Mike Connor [:mconnor]]

*** This bug has been marked as a duplicate of 252362 ***

Comment 4

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change