Open Bug 1490859 Opened 7 years ago Updated 3 years ago

Include the extension title in Browser Console "View source in Debugger → moz-extension://..." tooltips

Categories

(WebExtensions :: Developer Tools, enhancement, P5)

63 Branch
enhancement

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: from_bugzilla3, Unassigned)

References

Details

(Whiteboard: [dev-ux][addon-debugging])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180906162647 Steps to reproduce: 1. Encounter an error in the browser console 2. Hover over the source reference on the right side of it Actual results: I get a tooltip which says "View Source in Debugger → moz-extension://...". Because extensions often use a human-readable filename for their XPI and don't include an identifying comment header at the top of every source file, my only option for identifying what extension to report the bug on is to read the source and then identify the extension by what function the code performs. (eg. "This must be Awesome RSS. Nothing else I have installed should interact with RSS feeds in this way.") Expected results: The tooltip should also include the title of the extension which corresponds to the unhelpfully opaque UUID.
Hi, If I understand correctly from your report, you would be interested in an enhancement that would indicate the exact add-on that's causing the error in the browser console, instead of the shown error string. I'm assigning a component to get an opinion on this. Possibly a duplicate of 1490856
Severity: normal → enhancement
Component: Untriaged → Developer Tools
Product: Firefox → WebExtensions
See Also: → 1490856
Not quite. I would like to know the exact add-on in addition to the error string, not instead of it. Also, this is not a duplicate of bug 1490856. This is an enhancement request. That is a regression which I'll try to verify as being associated with out-of-process extensions later today.
Priority: -- → P5
Whiteboard: [dev-ux]
Whiteboard: [dev-ux] → [dev-ux][addon-debugging]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.