Closed
Bug 489529
Opened 16 years ago
Closed 14 years ago
Report path data parse error to error console
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
FIXED
People
(Reporter: takenspc, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
|
(deleted),
patch
|
Details | Diff | Splinter Review |
See bug 489328 comment 5
Bug 366130 probably depends of this bug.
|
Reporter | |
Comment 1•16 years ago
|
||
Patch.
My concern for using |ReportAttributeParseFailure| is that the error console item will be huge when the path data is very long.
|
|
Reporter | |
Comment 2•16 years ago
|
||
Oops! I attached wrong file as a patch!
Attachment #374031 -
Attachment is obsolete: true
|
||
Comment 3•16 years ago
|
||
You really need to show the part of the path that has failed to parse and not all of it. A few characters either side of the parse failure should suffice, and perhaps where the failure is as a number of characters from the start.
|
||
Comment 4•16 years ago
|
||
The patch in bug 489736 addresses the huge path issue by cropping the text, might be of interest.
|
|
||
Comment 5•16 years ago
|
||
The trouble with cropping the text is that if the error is in the 3000th character of d="..." then displaying the first x characters doesn't help all that much.
|
|
||
Comment 6•16 years ago
|
||
(In reply to comment #5)
No trouble! The sourceLine is split at the clumnNumber into two labels, the first is cropped at the start, the second at the end.
|
|
||
Comment 7•14 years ago
|
||
fixed by check in for bug 522306
You need to log in
before you can comment on or make changes to this bug.
Description
•