No UI for pref "Leaving a site that supports encryption"

VERIFIED FIXED in psm2.1

Status

()

Core
Security: PSM
P2
normal
VERIFIED FIXED
17 years ago
10 years ago

People

(Reporter: John Unruh, Assigned: David P. Drinan)

Tracking

1.0 Branch
psm2.1
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

17 years ago
1.) Edit > Prefs > Privacy/Security > SSL.
Note that there is no UI to set the pref "Leaving a site that supports 
encryption".
(Reporter)

Comment 1

17 years ago
Milestone 2.0
OS: Windows NT → All
Priority: -- → P3
Hardware: PC → All
Target Milestone: --- → 2.0
(Assignee)

Comment 2

17 years ago
-> p2
Priority: P3 → P2
nifty, r=db48x

Comment 5

17 years ago
cc'ing blake for sr=

Comment 6

17 years ago
cc'ing mpt/cotter to take a look at the wording.

Comment 7

17 years ago
Mass reassigning target to 2.1
Target Milestone: 2.0 → 2.1

Updated

17 years ago
Keywords: nsenterprise

Comment 8

17 years ago
Looks ok to me, except that `Redirection' should be `Redirecting'.

Comment 9

17 years ago
Created attachment 41239 [details] [diff] [review]
updated patch; Redirection -> Redirecting
(Assignee)

Comment 10

17 years ago
+<!ENTITY warn.insecurepost "Sending form data from an insecure page to an
insecure page">
+<!ENTITY warn.leavingsecure "Leaving a site that supports encryption">
+<!ENTITY warn.secureredirect "Redirecting from one secure site to another">
+<!ENTITY warn.secureredirecttoinsecure "Redirecting from a secure site to an
insecure site">


Use non-secure instead of insecure.

Fix that and r=ddrinan.

Comment 11

17 years ago
Created attachment 41301 [details] [diff] [review]
updated patch; insecure -> non-secure

Comment 12

17 years ago
<!ENTITY warn.enteringsecure "Entering a site that supports encryption">
<!ENTITY warn.enteringweak "Entering a site that uses low-grade encryption">

+<!ENTITY warn.insecurepost "Sending form data from a non-secure page to a
non-secure page">
+<!ENTITY warn.leavingsecure "Leaving a site that supports encryption">
+<!ENTITY warn.secureredirect "Redirecting from one secure site to another">
+<!ENTITY warn.secureredirecttoinsecure "Redirecting from a secure site to a
non-secure site">

I believe it would be more consistent (and accurate) to avoid the word "secure"
altogether, and also to describe things in terms of "pages" rather than "sites."
This can be done as follows:

Loading a page that supports encryption
Loading a page that uses low-grade encryption
Sending form data from an unencrypted page to an unencrypted page
Leaving a page that supports encryption
Redirecting from one encrypted page to another
Redirecting from an encrypted page to an unencrypted page

The above changes would also be consistent with my proposed patch for bug 44042. 

Question: Is this patch destined for the trunk only, which I assume means PSM
2.1? If it's destined for the branch it will require changes in the UI
translations, something I thought was no longer possible. It will also require
changes to help, which is still (barely) possible for 2.0.

Comment 13

17 years ago
Created attachment 41319 [details] [diff] [review]
updated patch; with sean's changes
(Assignee)

Comment 14

17 years ago
r=ddrinan.
sr=blizzard

Comment 16

17 years ago
Patch checked in.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
(Reporter)

Comment 17

17 years ago
Verified fixed on the trunk.
Status: RESOLVED → VERIFIED

Updated

13 years ago
Component: Security: PSM → Security: PSM
Product: PSM → Core

Updated

10 years ago
Version: psm2.0 → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.