Closed
Bug 21368
Opened 25 years ago
Closed 25 years ago
"JavaScript Error: uncaught exception" message
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: cyril_bortolato, Assigned: vidur)
References
()
Details
(Whiteboard: [HAVE FIX])
Overview Description:
Each time I load www.asymetrix.com, I get the following message in
the console window from which I started mozilla:
JavaScript Error: uncaught exception: [Exception... "Failure" code: "-214746725
9" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "http://www.asymetrix.co
m/ Line: 60"]
I saved the page source. Unfortunately when I tried to load it using file:/
etc.. no such messages showed up.
Step to reproduce:
1) go to www.asymetrix.com
Actual results:
The page displays normally.
Build date and platform:
M11 on Linux (RH 6.0, kernel 2.3.29)
Updated•25 years ago
|
Assignee: mccabe → vidur
Component: Javascript Engine → DOM Level 0
Comment 1•25 years ago
|
||
What you're seeing is a failure reported by some binary component that has an
API that's exposed to JavaScript. It's not a problem with JavaScript per se,
any more than an exception thrown from a Java class indicates a problem with
Java.
Reassigning to the DOM level 0 component, as it likely exposes the problem
interface to JavaScript.
borto - it's highly unlikely we'll get to this soon, UNLESS you can boil this
down to a simple testcase. Look at the line that failed - can you make a
webpage that has just that code and still fails in the same way?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [HAVE FIX]
Assignee | ||
Comment 2•25 years ago
|
||
The problem was actually our implementation of the navigator.plugins collection.
We were returning an error code as opposed to just null or undefined if a plugin
wasn't found. I have a fix in my tree. It might have to wait till M13.
Reporter | ||
Comment 3•25 years ago
|
||
Here's a testcase that reproduces the error:
<script language="JavaScript">
function check_plugin(plugin) {
if (navigator.plugins && navigator.plugins[plugin])
return true;
}
</script>
<body onLoad="return check_plugin('foobar') ;"> </body>
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•25 years ago
|
||
Fixed on 12/14/1999.
You need to log in
before you can comment on or make changes to this bug.
Description
•