Update documentation of unknown cert issuer dialog

RESOLVED FIXED in seamonkey2.0a1

Status

SeaMonkey
Help Documentation
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: stefanh, Assigned: stefanh)

Tracking

Trunk
seamonkey2.0a1

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
Bug 343253 changed the dialog a bit.
(Assignee)

Updated

11 years ago
Summary: Update documantation of unknown cert issuer dialog → Update documentation of unknown cert issuer dialog
(Assignee)

Comment 1

11 years ago
Created attachment 270796 [details] [diff] [review]
Update documentation

Some thoughts:

-    Select this option to accept the certificate temporarily and connect to the
-    website. Certificate Manager will recognize this certificate as legitimate
-    identification only until the next time you launch the browser. You may see
-    the same alert the next time you attempt to visit the website.</li>

I think this is wrong, so I re-wrote it. Have MailNews and Navigator open, close Navigator: wouldn't that result in the cert still accepted? I just tried closing the browser on mac (which won't quit SeaMonkey). Can you try on windows?

Note also that I focused on the buttons - the 2 acceptance options might suffer a bit. But I didn't really knew how to solve it the "View Certificate" button isn't optionally positioned...(Make your choice and then View the cert?).
Attachment #270796 - Flags: review?(iann_bugzilla)

Comment 2

11 years ago
Comment on attachment 270796 [details] [diff] [review]
Update documentation

r=me, definitely better than what is there at the moment.
Attachment #270796 - Flags: review?(iann_bugzilla) → review+
(Assignee)

Comment 3

11 years ago
Checking in suite/locales/en-US/chrome/common/help/cert_dialog_help.xhtml;
/cvsroot/mozilla/suite/locales/en-US/chrome/common/help/cert_dialog_help.xhtml,v  <--  cert_dialog_help.xhtml
new revision: 1.21; previous revision: 1.20
done
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.