Closed Bug 102289 Opened 24 years ago Closed 24 years ago

Certain documentation for Security has browser UI specific information

Categories

(Core Graveyard :: Security: UI, defect, P2)

1.0 Branch
defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: radha, Assigned: radha)

References

Details

(Keywords: topembed)

Attachments

(1 file, 2 obsolete files)

Certain documentation (probably dialog messages) has references to mozilla/netscape browser UI. This does not work well in embedded applications that have their own UI. Following are 2 segments of code that has mozilla UI specific info. \mozilla\security\manager\ssl\resources\locale\en-US\pipnss.properties(150):SSLDisabled= "You cannot connect to %S because SSL is disabled. To change this setting, <XXX BEGIN CHANGE> choose Preferences from the Edit menu, click Privacy and Security, and click the subcategory SSL." <XXX END CHANGE> \mozilla\security\manager\ssl\resources\locale\en-US\pipnss.properties(151):SSL2Disabled= "You cannot connect to %S because SSL version 2 is disabled. To change this setting, <XXX BEGIN CHANGE> c hoose Preferences from the Edit menu, click Privacy and Security, and click the subcategory SSL." <XXX END CHANGE>
-> javi.
I'm assuming Jud meant to reassign this bug.
Assignee: mstoltz → javi
Component: Security: General → Client Library
Product: Browser → PSM
Version: other → 2.1
Priority: -- → P2
Target Milestone: --- → Future
Giving user input on what he or she needs to do to correct a problem, including helping in navigating the UI is a must. What is the accepted way of doing this?
cc'ing german. I'm not sure what the right thing is. I'd actually argue though that "documentation" (user manuals, online help) is the immediate answer though. Mozilla no longer controls the UI that uses the underlying modules, and propegating "instructions" at this level isn't right.
Keywords: mozilla0.9.5
I think the part that describes the UI can be put in a separate property and referenced independantly in the js or xul file. Then the embedding application can replace the mozilla UI property string with its own UI description or omit it, if it doesn't want reference to the UI.
Attached patch Initial patch (obsolete) — Splinter Review
I have attached a patch which segregates the UI information from the original property string. This enables a embeddor to either ignore the UI info or replace it with their UI info. I think simply not defining SSLDisabledUI in the property file will render the message without the UI info. I hope this will be a reasonable solution to the embeddors. This patch builds in Windows. (I haven't tried linux yet.) I don't know how to test this. I don't even know when and where this message will show up. Can some one in the security team try out the patch and make sure that mozilla works jsut as it should be.
This seems like a reasonable workaround, but I still don't think we should be displaying instructions in dialogs. I suggest we pull the instructions text altogether, and just put instructions in our documentation.
Attached patch Updated patch (obsolete) — Splinter Review
Attachment #51922 - Attachment is obsolete: true
I have attached a patch that just removes the UI references from dialog messages. I understand that the UE group is fine with this kind of changes. For more discussion on the see bug 102288.
Taking from jave, as I have the patch and trying to get it in ASAP.
Assignee: javi → radha
that's not a patch, its a "cvs status" :)
Attachment #52259 - Attachment is obsolete: true
cc'ing security folks. r=valeski on the mods, but we need to have they'r buyin' before checking this in.
Attachment #52584 - Flags: superreview+
sr=alecf for once you have their acceptance.
QA Contact: bsharma → junruh
Attachment #52584 - Flags: review+
Comment on attachment 52584 [details] [diff] [review] the right patch reviewed. This must be checked in by somebody with the proper access to the security area. Radha, you don't have access, so somebody in PSM will need to do it.
Checked in to trunk, marking resolved.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
adding dependency for tracking purposes.
Blocks: 70229
Verified on 10/12 Win98 trunk.
Status: RESOLVED → VERIFIED
Keywords: edt0.9.4
minusing. not needed on the branch.
Keywords: edt0.9.4edt0.9.4-
Keywords: topembed
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: