Closed
Bug 23241
Opened 25 years ago
Closed 25 years ago
(harmless?) javascript error when viewing a message
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: sspitzer, Assigned: mscott)
Details
on today's build, when I view a message, this gets sent to the console:
"JavaScript Error: uncaught exception: Access denied to XPConnect service."
this wasn't a debug build, so I can't tell where it is coming from.
so far, it seems harmless, as everything appears to work fine.
my first guess is somewhere we have some javascript that is being loaded without
a chrome url, so it for security reasons, it is denined access to xpconnect.
Assignee | ||
Comment 1•25 years ago
|
||
I don't see this error using the commercial build for 1/6 this morning nor my
debug builds on linux or windows from last night. Seth thinks he may have just
had a bad build.
Reporter | ||
Comment 2•25 years ago
|
||
nope, it's real. but so far, it still seems harmless.
using the commericial linux build from today, I get this in my console:
In ThreadPaneOnClick
JavaScript Error: uncaught exception: Access denied to XPConnect service.
JavaScript Error: uncaught exception: Access denied to XPConnect service.
JavaScript Error: uncaught exception: Access denied to XPConnect service.
JavaScript Error: uncaught exception: Access denied to XPConnect service.
JavaScript Error: uncaught exception: Access denied to XPConnect service.
WEBSHELL+ = 6
Reporter | ||
Comment 3•25 years ago
|
||
note: I don't see this with the commercial build that I built, but the one from
sweetlou has it.
Assignee | ||
Comment 4•25 years ago
|
||
I'm not seeing this in the builds anymore....somehow some way...it just went
away...=)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking verified as of 2000-02-15-09m14 mozilla build, linux rh6.0:
Based on mscott's last comments and I don't see it, although I never did.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•