300167 - When security.warn_submit_insecure is set to true, the Security Alert dialog box shows up twice on all insecure form submissions.

Status: RESOLVED DUPLICATE of bug 180962

(Firefox :: Settings UI, defect)

Description

[John Jung]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I want to know when Firefox is sending form data, so I set
security.warn_submit_insecure to true.  When I go to any insecure Web page
(www.yahoo.com or www.google.com for example), enter some data into the form
field, and submit the form, the Security Alert dialog box shows up.

I leave the "Alert me whenever I submit information that's not encrypted"
checked on, and click Continue.  This results in the exact same dialog box
appearing again.  Leaving the checkbox on and clicking Continue again, the form
is finally submitted.

If I uncheck either the first or second check boxes, I never get the alert
dialog for any form submission.

Reproducible: Always

Steps to Reproduce:
1. Modify user.js or use the Preferential Extension and modify
   security.warn_submit_insecure to true.
2. Go to any Web page with a text form submission.
3. Type in some text and submit the form.

Actual Results:  
Two identical alert dialog boxes.

Expected Results:  
I would expect only one dialog box.  The first one is reasonable since it's
alerting me of a potential security risk.  But after acknowledging it, the
second one shouldn't show up.


This may be related to bug #281515.

Comment 1

[William Bumgarner [:zsinj]]

Could you download a nightly build (http://www.mozilla.com/developer) and report
your findings with this newer version?

Comment 2

[Steve England [:stevee]]

WFm Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b3) Gecko/20050709
Firefox/1.0+ ID:2005070910

Comment 3

[John Jung]

Deer Pack Alpha 2 behaves correctly.

Comment 4

[Phil Ringnalda (:philor)]

Yep, |fixed| in bug 180962.

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