Closed
Bug 413049
Opened 17 years ago
Closed 17 years ago
error console ignores line number annotations
Categories
(Core Graveyard :: Error Console, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 246286
People
(Reporter: myk, Unassigned)
Details
I could've sworn I'd filed this bug before, but I can't find it now. The Error Console seems to be (again?) ignoring line number annotations for preprocessed chrome JavaScript files. It reports the line number where the error occurred in the preprocessed file rather than the original source file. It seems like it should (perhaps additionally) report the line number where the error occurred in the original source file.
Comment 1•17 years ago
|
||
Did the Error Console ever recognize line number annotations in the first place?
Reporter | ||
Comment 2•17 years ago
|
||
(In reply to comment #1) > Did the Error Console ever recognize line number annotations in the first > place? I thought it did at one point, although I can't say for sure.
Comment 3•17 years ago
|
||
I would think that this feature would have messed up the ability of the Error Console to open a view source window focused on the correct line.
Comment 4•17 years ago
|
||
(In reply to comment #2) > (In reply to comment #1) > > Did the Error Console ever recognize line number annotations in the first > > place? > > I thought it did at one point, although I can't say for sure. Perhaps you're thinking of bug 246286? That bug's patch to the preprocessor to add the "@line" markers was checked in, but the code to make use of it never was. Seems to me like this is a duplicate of that bug.
Reporter | ||
Comment 5•17 years ago
|
||
That's exactly what I was thinking of. Thanks Gavin!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•