Open
Bug 1508589
Opened 6 years ago
Updated 2 years ago
URL-ify filename clickable in Error messages
Categories
(DevTools :: Console, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: nachtigall, Unassigned)
Details
Attachments
(1 file)
19.53 KB,
image/png
|
Details |
See screenshot. There's one source for the error ("at AppRoutedWrapper.js:70" which is my file where the error happens), but I cannot click it. It should be clickable. That's what I would like to do in such a situation most of the time. I think it was clickable (not 100%) sure before the debugger stacktrace component was integrated as part of bug 1390768.
Comment 1•6 years ago
|
||
I don't think it was added by Bug 1390768, for the very reason that it's not obvious what should be done with a single filename. (So, just to get this out of the way, having the fill url won't render a string either :) , we should use the String reps, which has all the linkification logic to render every message we put in the console ). For this given case, I'm not sure there's a good fix, other than ask React to print the full url to the component (but I don't think it's trivial on their end). We could just guess and try to open the filename in the root folder, but from experience, react components are usually buried down a deep hierarchy, and we'd fail most of the time.
No longer blocks: 1390768
Updated•6 years ago
|
Priority: -- → P3
Summary: Console: Collapsed stacktraces should allow to click on first source of message → URL-ify filename clickable in Error messages
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•