Closed
Bug 344335
Opened 19 years ago
Closed 19 years ago
JavaScript parse errors in XUL files are not reported
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 324142
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file)
|
221 bytes,
application/vnd.mozilla.xul+xml
|
Details |
Steps to reproduce:
1. Load the testcase.
Result: Only see "Error: foop is not defined".
Expected: See "Syntax error", followed by "Error: foop is not defined".
|
Reporter | |
Comment 1•19 years ago
|
||
|
|
Reporter | |
Comment 2•19 years ago
|
||
2. Look in Tools > Error Console.
|
||
Comment 3•19 years ago
|
||
Related to bug 324142?
|
||
Comment 4•19 years ago
|
||
*** Bug 352006 has been marked as a duplicate of this bug. ***
|
|
||
Comment 5•19 years ago
|
||
I'd like to add that this makes extension development a lot more difficult than it should be. Since extensions often wrap their functions in an object to avoid conflicts, you get a generic "wrapperObject is not defined, line: 1" which is not at all helpful.
OS: Mac OS X 10.4 → All
Hardware: Macintosh → All
|
||
Comment 6•19 years ago
|
||
Looking at the bug 324142 now.
/be
*** This bug has been marked as a duplicate of 324142 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•