Closed Bug 62196 Opened 24 years ago Closed 24 years ago

javascript error in securityUI.js

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: ddrinan0264)

Details

JavaScript error: chrome://communicator/content/securityUI.js line 31: Components.classes['@mozilla.org/secure_browser_ui;1'] has no properties
I like to suggest: Can't we say you need to check your source first at w3c, before filing a bug here? At this page (for example): http://www.mozilla.org/quality/help/bugzilla-helper.html
SecurityUI is the lock icon, right? Reassigning to Crypto.
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: ckritzer → junruh
Man this is what I'm looking for, I lost it. Sorry, but my comment in not filed for this bug! Don't ask me how, but it's wrong! How can that be? Friendly, HJ
I have also run into this bug using 2000-12-27 nightly on RH 6.2. Simply runnin g this sample from Mozilla itself: http://lxr.mozilla.org/seamonkey/source/xpcom/sample/xpconnect-sample.html Illustrates the problem.
This appears to be fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Any idea what checkin fixed this? I'm seeing it in my OpenVMS M0.7 build.
I'm also seeing it my mozilla nightly with Build ID 2001013021 on Solaris 7.
reopen based on users comments.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I have a similar bug (not quite identical; it says the JS error occurs on line 0) both when I click the lock icon, as was mentioned, and when I try to open the "Personal Security Manager" (something I haven't seen mentioned here). I am using Mozilla 0.8. I installed from an RPM which I got from the official web-site. Also, in the way of a quick fix, if there is a way to disable TLS without using the security manager (edit a text configuration file?) I'd very much appreciate an email (kenny@kennypearce.net). Thank you.
I appologize for my previous entry, which was a wetware problem, rather than a mozilla bug (meaning I'm an idiot and didn't install the mozilla-psm package). Sorry!
PSM 2.0 is now part of the mozilla and commercial builds and has fixed alot of UI and ssl bugs that were in PSM 1.X. I'm doing a mass setting of bugs to be FIXED. If you believe that I've closed a bug in error, please re-open it. Thanks.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Verified fixed.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
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.