Actions
Feature #6534
open
Error messages with line numbers
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2024-09-15
Due date:
% Done:
0%
Estimated time:
Applies to JS Branch:
2
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
Many error messages are cuite cryptic:
Uncaught XError: No containing document for key()
Doesn't tell me the name of the key. But more importantly it doesn't give me the line/col numbers. Debugging this in an async stylesheet is a PITA...
Updated by Martynas Jusevicius about 1 month ago
Another example:
Uncaught XError: Failed to call method function construct() {
[native code]
}
Updated by Michael Kay about 1 month ago
It's great to have feedback on poor diagnostics, but improving them can generally only be done on a case-by-case basis, so it's important that we can reproduce the problem.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page
.