Closed Bug 129044 Opened 23 years ago Closed 11 years ago

javascript strict warnings in msgHdrViewSMIMEOverlay.js

Categories

(MailNews Core :: Security: S/MIME, defect)

Product:
MailNews Core
Component:
Security: S/MIME
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: bugzilla, Unassigned)

References

Details

(Whiteboard: [kerh-cuz] [closeme 2013-09-29])

if PSM is not installed I'm getting this when starting mail&news: Warning: reference to undefined property Components.interfaces.nsICMSMessageErrors Source File: chrome://messenger-smime/content/msgHdrViewSMIMEOverlay.js Line: 31 20020304
S/MIME is an extenstion which requires PSM. If PSM is not installed, the extension should not be used either.
Status: NEW → RESOLVED
Closed: 23 years ago
Priority: -- → P3
Resolution: --- → INVALID
Target Milestone: --- → 2.2
You should *never* get strict warnings. I dont care if PSM is installed or not. You just have to strengthen the check. something like: if "nsICMSMessageErrors" in Components.interfaces bla bla bla
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
QA Contact: alam → carosendahl
I'm taking this...
Assignee: ssaux → Morten
Status: REOPENED → NEW
Status: NEW → ASSIGNED
Target Milestone: 2.2 → Future
see also bug 129042
Assignee: Morten → nobody
Status: ASSIGNED → NEW
Product: PSM → Core
Whiteboard: [kerh-cuz]
QA Contact: carosendahl → s.mime
Blocks: 296661
Version: psm1.01 → 1.0 Branch
Version: 1.0 Branch → Trunk
Product: Core → MailNews Core
(In reply to comment #4) > see also bug 129042 was wontfixed...so is this bug invalid, despite comment 2?
Severity: normal → minor
Priority: P3 → --
Target Milestone: Future → ---
Is this bug still active? Should it stay open?
Flagging needinfo? for answer to Comment 6.
Flags: needinfo?(bugzilla)
Whiteboard: [kerh-cuz] → [kerh-cuz] [closeme 2013-09-29]
Status: NEW → RESOLVED
Closed: 23 years ago → 11 years ago
Flags: needinfo?(bugzilla)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.